On Fri, Mar 9, 2018 at 11:17 AM, Alec Warner <[email protected]> wrote: > > In contrast with disposable containers: > > Automated build process for my containers. > > If there is a bug in the build, I can throw my buggy containers away and > build new ones. > > Containers are encouraged to be stateless, so logging in to the container as > root is unlikely to scale well; the containers are likely to remain 'clean.' > > If my containers are dirty, I can just throw them away and build new ones. > > If I need to change roles, I can just destroy the webnode container and > deploy a LDAP node container. > > The containers are nominally stateless, so there is less chance of 'gunk' > building up and surprising me later. It also makes the lifecycle simpler. > > Obviously its somewhat harder for stateful services (databases, etc.) but I > suspect things like SANs (or Ceph) can really provide the storage backing > for the database. > (database "schema" cleanliness is perhaps a separate issue that I'll defer > for another time ;p) >
Certainly this is a great way to approach things, but it is also not the process we have in our handbook, and therefore it seems a bit much to expect users to actually be following it. If every one of our profiles shipped with an ansible config file or similar that just results in a working image with a few edits this would be somewhat more practical, though I'm not sure I've really seen a clean solution for something like "docker on the desktop." Docker won't even fetch an IP address from my router using DHCP... -- Rich
