So I’ve been self-hosting for a few years now…got a decent setup…
But I only really got into docker-compose in the last few months… I mean, I’ve used it through the “Apps” in TureNAS, but never directly…
I ran a mastodon host on a VM (giant pain in the ass) and a few other things that weren’t available as apps, but never mainstream…
Once I got into it, I managed to get everything moved over to truenas as docker containers…
Last week it saved my ass…the AC in the house failed…and I was able to shut down everything save the Truenas (with a fan pointed at the front of the server) and keep everything up and running throughout…
So it’s been helpful to know, and an awesome learning experience. (I’m happiest when I’m learning new things)
My question is this…
How do you back them up? I mean, I have snapshot backups of my docker-volume ZFS dataset, and replicate that to a remote host…but I’m not even sure I’d know how to recover it if I had to…is it just a file copy and restart?
Yeah, I bind mount the config inside a config directory just below the compose file, and the state (databases, files, etc) to a seperate storage location that makes sense. The compose and config gets added to git and pushed to a forge, while the storage directories are backed up like normal (in my case, zfs snapshots pushed to another computer and then restic backs up those cold files to b2. The volumes are ephemeral.