I know, and read, a lot of posts here about backing up Docker volumes and data. The problem is that everyone has different setup, context and needs. So I need some help deciding what is best (and easy to manage) solution for my use case.

My setup is fairly simple. I only use docker compose files, have one service per directory and all services are using named volumes. Some have driver: local to mount a local folder with config (always located in the same directory of the service). Each docker-compose.yaml file has a backup container which is offen/docker-volume-backup to backup the volumes. These backups are stored in a different folder (the same for all backups /media/storage/backups/). I also have a service with Duplicati to backup the volume backups and some extra data (Nextcloud) to a remote server.

The reason why I use offen/docker-volume-backup is to shut down some containers for extra safety but I'm not sure I actually need this because I'm the only user and I'm not planning on opening my server for other user.

Before I implemented docker-volume-backup and Duplicati all containers used bind mounts because that's less abstract for me, to actually see the files.

Now, my question is: is this a good setup? Is there an easier setup with less components/steps? Is it, for example, also good if I go back to bind mounts and just backup everything with Duplicati when I'm asleep at night?

Thank you for all the great advise!

Homer dashboard with custom theme

After lurking for years on this subreddit I finally bought a mini PC for the soul purpose of experimenting with self hosting. So the past few days I've been learning about Docker and stealing all your docker-compose files and combined them into something I could actually use.

The code is available on Github. Please give me some feedback because I'm 200% sure I did a lot the wrong way. What I've however learned from you guys is to document what you're doing when you're doing it instead of later (never).