Comment on Docker Backup Stratagy
catloaf@lemm.ee 9 months ago
Bind mounts. I’ve never bothered to figure out named volumes, since I often work with the contents outside Docker. Then I just back up the whole proxmox VM. (Yes I’m aware proxmox supports containers, no I don’t plan to convert, that’s more time and effort for no meaningful gain to me.)
You can restore that backup to a new VM. I just make sure it boots and I can access the files. Turn off networking before you boot it so that it doesn’t cause conflicts.
Yep, bind mount the data and config directories and back those up. You can test a backup by spinning up a new image with the data/config directories.
This is both easy and generally the recommended thing I’ve seen for many services.
The only thing that could cause issues is breaking changes caused by the docker images themselves, but that’s an issue regardless of backup strategy.
ChapulinColorado@lemmy.world 9 months ago
After getting a NAS to replace my raspberry pi 4 as a home server, I literally just SCPd the bind mounts and docker compose folder, adjusted a few env variables (and found out of a few I needed to add for things like the uid/guid the NAS used as default for the media user I created) and it took maybe 30 minutes total to be back and running. Highly agree with you from experience.
catloaf@lemm.ee 9 months ago
Yup, it works great. I actually did it myself when migrating from a centos to debian host. Worked first try, no issues (except one thing that was already broken but I didn’t know because I hadn’t accessed it recently). Containers are great for this.