Container structure simplification and volume management #219
Description
Hello all,
Many people spoke to me about the structure data/files/exec of the container, which may not be state of the art of today.
Indeed, Docker introduced some time ago an extensive management for volumes, which can now be independently managed. Before we needed to create what we called "data containers" (here data and files) to ensure we don't lose the volume each time we update the container executing the binary (here exec). I agree we don't need data/files/exec anymore, this confuse people and make the use of external images quite difficult.
For example, for a Odoo10 + Postgres service, I suggest the following structure :
Odoo 10 + Postgres
- Postgres
- Odoo 10
-- Odoo 10 SSH (child of Odoo 10 to allow access to customers, container optionnal, the odoo binary is in Odoo10)
This structure means we can deploy child container under a container effectively deployed on the node. This was impossible before, I expect some heavy change in core to make it possible.
Then, I'll start working on simplifying the template, so we only need one container. At the same time, the volume management will be improved so they can be independently managed in clouder, making sure we don't risk losing data.
I am migrating my own infrastructure on the master branch. I want to do this before the migration, then this shall be done in the next days.
cc @lasley @samuellefever