...
However, interestingly enough as I used LXC more, I started to appreciate the spirit of Docker's approach to being so marketing (which will mean it will do well), documentation and spirit of being restrictive. From the view of writing applications and operating them:
- Ephemeral - Being stateless you build must externalize the right things (logs, application property files) from day 1.
- Single Process as Best Practice - I lose SSH access, but I then stop thinking of stacks (OS, Java, JEE Server, Application Code) and instead of a single package.
- No Upgrading, Just Rebuilt - Rebuild your Day 1 you script to update your application and OS . Why upgrade, update your script and automate from day 1.creating consistency.
It's a fundamental mind shift. If forces both Ops and Developers into a repeatable automated approach to building servers and coding applications. This shifts work instead to using good orchestration software (which I am in process of researching). The Docker base OS template is pared down to a single app environment and does not endorse an init, services, daemons, syslog, cron or running multiple applications.
...