rickmak/dockup repository overview

⁠Dockup

Docker image to backup your Docker container volumes

Why the name? Docker + Backup = Dockup

⁠Usage

You have a container running with one or more volumes:

$ docker run -d --name mysql rickmak/mysql

From executing a $ docker inspect wordpress we see that this container has two volumes:

"Volumes": {
  "/var/www/html": {}
}

⁠Backup

Launch dockup container with the following flags:

$ docker run --rm \
--env-file env.txt \
--link mysql
--volumes-from wordpress \
--name dockup rickmak/dockup:latest

The contents of env.txt being:

AWS_ACCESS_KEY_ID=<key_here>
AWS_SECRET_ACCESS_KEY=<secret_here>
AWS_DEFAULT_REGION=us-east-1
BACKUP_NAME=mysql
PATHS_TO_BACKUP=/etc/mysql /var/lib/mysql
S3_BUCKET_NAME=docker-backups.example.com
MYSQL_USER=root
MYSQL_PASS=
MYSQL_DB=db
RESTORE=false

dockup assume the bucket with name S3_BUCKET_NAME already created. The paths in PATHS_TO_BACKUP will be tarballed, gzipped, time-stamped and uploaded to the S3 bucket.

⁠Restore

To restore your data simply set the RESTORE environment variable to true

• this will restore the latest backup from S3 to your volume.

⁠A note on Buckets

These rules are enforced in some regions.

AWS S3 Regions⁠