rkCSD/docker-database-autobackup
3
0
Fork 0
mirror of https://kolaente.dev/konrad/docker-db-backup.git synced 2026-01-10 02:50:08 +01:00
Code Issues Projects Releases Wiki Activity

feat: add support for labels to discover additional containers

Browse Source
This commit is contained in:
kolaente
2022-08-09 11:02:47 +02:00
parent 064d2ce66e
commit 96d61fd6e0
2 changed files with 12 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
README.md
View File

@@ -14,11 +14,18 @@ Simply point it at your docker socket, mount a backup volume and be done:
docker run -v $PWD/backups:/backups -v /var/run/docker.sock:/var/run/docker.sock kolaente/db-backup
```
The tool will find all database containers and create backups of them periodically. It will also discover new containers
The tool will find all database containers running an official [`mysql`](https://hub.docker.com/_/mysql),
[`mariadb`](https://hub.docker.com/_/mariadb) or [`postgres`](https://hub.docker.com/_/postgres) image and
create backups of them periodically. It will also discover new containers
as they are started and won't try to back up containers which have gone away.
When running, all backups for the current run are time-stamped into a sub folder of the backup directory (see below).
### Using labels
To make the backup tool discover other non-offical containers as well you can add the label `de.kolaente.db-backup` to
any container with a value of `mysql` or `postgres` to treat it as a mysql or postgres container.
### Docker Compose
If you're running docker-compose, you can use a setup similar to the following compose file to run the backup: