I’m starting to appreciate docker on my home server. Running various apps and services in a container allows me to keep my operating system (Debian/OpenMediaVault) as clean as possible without having to run lots of virtual machines.
a) why/under what circumstances this makes sense
b) how it works.
Ad a), here is what I found so far:
I do run docker as root and my machine is (for the time being) not exposed to the internet.
Hm, not sure how this is an advantage as it also means: I have to make sure everything I want to backup is indeed mounted. I think I prefer to rely on duplicacy’s
filter file (as well as
. nobackup files and, if need be, symlinks) for managing what is or is not backed up. Why introduce a second selection layer?
So is there anything else to say about dockerizing duplicacy?
Ad b), what I’m mainly wondering is: how does duplicacy get access to the files it should back up? I realize that the answer might already be up there in this very post: you have to mount everything. But if this is correct, then I’d anticipate all kinds of access problems which I probably wouldn’t have when running duplicacy as root on the server directly?
I’d also anticipate confusions around repository paths as these will we relative to the container, not the host. Not unsolvable, of course, but adding friction.
Please let me know if I’m missing any important points (I’m pretty sure I am).