In contrast virtual machine runs both kernel and userspace (via hypervisor that can either run on the host OS or sit under it).ĭocker is useful to isolate dependencies and convert a complex app consisting from multiple interacting services and libraries into one single disposable monolithic entity that operates on some data mapped out to the host system. It provides entirely separate user mode environment but relies on host systems kernel. Please let me know if I’m missing any important points (I’m pretty sure I am).Ī) why/under what circumstances this makes sense

Not unsolvable, of course, but adding friction. I’d also anticipate confusions around repository paths as these will we relative to the container, not the host. 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? So is there anything else to say about dockerizing duplicacy?Īd 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.

I totally see the advantage here but it applies exactly once (upon first setup) and I have learned that this is also easily solved with a tunnel. Eliminates the need to start the application before modifying the port it listens on (as has been mentioned, port 8080 will commonly be in use on an existing (shared) server.

Duplicacy upgrading