Personally, I’m mostly struggling with what data is stored where and how persistence is achieved. I have no issues getting services up and running with docker, but I’m paranoid about messing up my data.
If the service plainly stores content to a database, I have no problem backing up the database. But the variety of services offered via “simply run this docker command” come, as diverse the contents are. Between stored content (e.g. photos, documents, …), metadata and configuration, I feel lost on how to handle this, when it comes to updates.
In comparison, when I set up an LXC container, where I take care of each dependency and step of the setup myself, I’m more aware on what is stored where and can take care of my data.
Personally, I’m mostly struggling with what data is stored where and how persistence is achieved. I have no issues getting services up and running with docker, but I’m paranoid about messing up my data.
If the service plainly stores content to a database, I have no problem backing up the database. But the variety of services offered via “simply run this docker command” come, as diverse the contents are. Between stored content (e.g. photos, documents, …), metadata and configuration, I feel lost on how to handle this, when it comes to updates.
In comparison, when I set up an LXC container, where I take care of each dependency and step of the setup myself, I’m more aware on what is stored where and can take care of my data.