mirror of synced 2026-05-02 10:30:34 +00:00

Backup and restore Docker volumes to S3-compatible storages.

Shell 85.2%
Dockerfile 14.8%

Find a file

Romein van Buren 044ddcdbda Update documentation		2025-05-04 18:03:24 +02:00
.github/workflows	Use v3 login action	2025-05-04 13:31:41 +02:00
src	Add restore script	2025-05-04 18:03:15 +02:00
test_image	Fix some bugs, it is working now!	2025-05-04 13:54:42 +02:00
.dir-locals.el	add .dir-locals.el	2022-09-25 13:46:26 -04:00
.dockerignore	add docker-compose.yaml for development/testing	2022-07-03 13:43:54 -04:00
.env.example	Adapt postgres-baskup-s3 to backup Docker volumes instead of Postgres databases	2025-05-04 13:18:07 +02:00
.gitignore	Adapt postgres-baskup-s3 to backup Docker volumes instead of Postgres databases	2025-05-04 13:18:07 +02:00
docker-compose.yaml	Fix some bugs, it is working now!	2025-05-04 13:54:42 +02:00
Dockerfile	Add restore script	2025-05-04 18:03:15 +02:00
LICENSE.txt	Adapt postgres-baskup-s3 to backup Docker volumes instead of Postgres databases	2025-05-04 13:18:07 +02:00
README.md	Update documentation	2025-05-04 18:03:24 +02:00

README.md

docker-volume-s3-backup

Introduction

This project provides a Docker image that periodically backs up a Docker volume to AWS S3 as a gzipped tape archive, and can restore a backup as needed.

Usage

Backup

Example docker-compose.yml:

services:
  my_service:
    image: ...
    volumes:
      data:/app/some-data-dir

  volume_backup:
    image: garraflavatra/docker-volume-s3-backup
    volumes:
      data:/data/folder1
    environment:
      BACKUP_NAME: myvolume         # required
      SCHEDULE: '@weekly'           # optional
      BACKUP_KEEP_DAYS: 7           # optional
      PASSPHRASE: passphrase        # optional
      S3_REGION: region             # or set S3_ENDPOINT if you do not use AWS
      S3_ACCESS_KEY_ID: key         # alias S3_ACCESS_KEY
      S3_SECRET_ACCESS_KEY: secret  # alias S3_SECRET_KEY
      S3_BUCKET: my-bucket          # required
      S3_PREFIX: backup             # required

You can mount as many folders into /data as you like. Everything in /data is copied to your S3 storage in a single .tar.gz.
The SCHEDULE variable determines backup frequency. See go-cron schedules documentation here. Omit to run the backup immediately and then exit.
If PASSPHRASE is provided, the backup will be encrypted using GPG.
Run docker exec <container_name> sh backup.sh to trigger a backup ad-hoc.
If BACKUP_KEEP_DAYS is set, backups older than this many days will be deleted from S3.
Set S3_ENDPOINT if you're using a non-AWS S3-compatible storage provider.

Restore

Caution

All existing files will be replaced by the backup content!

From latest backup

docker exec <container_name> sh restore.sh

Note

If your bucket has over 1000 files, the latest may not be restored – the S3 ls command is issued only once.

From specific backup

docker exec <container_name> sh restore.sh <timestamp>

Development

You can use the Docker Compose file in the root with your own S3 bucket for development and testing.

cp .env.example .env
# fill out your secrets/params in .env
docker compose up -d

Acknowledgements

This project is a modification of the excellent eeshugerman/postgres-backup-s3, which in turn is a fork and re-structuring of schickling/postgres-backup-s3 and schickling/postgres-restore-s3.

Copyright

Licensed under the MIT license.

README.md Unescape Escape