Our take
- Activity
- 65
- Community
- 67
- Issues
- 33
- Pull requests
- 74
+23 stars in the last 30 days
- Merges more pull requests than 76% of the projects we track
- Slower to close issues than 91% of the projects we track
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
4,078Forks
161Change since Nov 16, 2026: +1 stars·0 forks
Overview
offen/docker-volume-backup backs up Docker volumes without requiring backup logic inside the application container. It can run scheduled backups alongside an existing Docker setup or perform a one-off backup, sending archives to local storage, remote storage, or both.
It is a fit for people managing Docker Compose or Swarm deployments who want a configurable backup process across multiple storage destinations. See the project documentation for the full configuration reference and recipes.
Key Features
- Runs as a lightweight companion Docker container.
- Supports recurring and one-off volume backups.
- Writes backups to a local directory or compatible S3, WebDAV, Azure Blob Storage, Dropbox, Google Drive, or SSH storage.
- Can rotate old backups when configured.
- Supports GPG encryption of backups.
- Can send notifications about successful or failed backup runs.
- Can stop and restart selected containers during backup to help preserve data consistency.
Use Cases
- A Docker Compose operator wants scheduled backups of application data volumes without adding backup code to the application.
- A small team wants local archives alongside copies in remote storage for recovery planning.
- A self-hosting administrator needs one-off volume backups before a migration or maintenance operation.
- An operator wants to encrypt backup archives and receive notifications when backup runs fail.
Getting Started
For a one-off backup, mount a volume and run the image with the backup entrypoint:
docker run --rm -v data:/backup/data --entrypoint backup offen/docker-volume-backup:v2
Configure the destination and credentials using environment variables or an env file. For recurring backups and complete setup details, see the README and configuration reference.
Considerations
- Remote destinations require the appropriate credentials and configuration; a local archive requires a directory or volume mounted at
/archiveunless its location is changed. - Stopping containers during backup requires access to the Docker socket and the relevant container labels. Mounting the socket gives the backup container Docker control capabilities, so consider whether that access is appropriate for your setup.
- The project creates backups, but restore procedures and recovery testing remain part of the operator's responsibility.
- The README advises pinning a release tag in production rather than using
latest.
Found this useful?
Share it with someone who would like docker-volume-backup.