13 karma · joined October 20, 2014
my public key: https://keybase.io/justingood; my proof: https://keybase.io/justingood/sigs/bU5WuVQ0JmROZ_E0UBUQawSJ8BqdkLWhMakHTYG3hvw
The three types are, for example: http://oiswww.eumetsat.org/IPPS/html/latestImages/EUMETSAT_M... http://oiswww.eumetsat.org/IPPS/html/latestImages/EUMETSAT_M... http://oiswww.eumetsat.org/IPPS/html/latestImages/EUMETSAT_M...
We originally tried the docker module in Ansible but found it had a few problems. There's been a lot of work on it since, and I expect it will be in a much better state when Ansible 2.0 is released.
We eventually settled on having Ansible build an AMI for us that can then be spun up by as part of a Cloudformation template (also initiated by Ansible).
We've actually been moving further and further away from having Ansible handle the configuration management side of things, and deal with Orchestration primarily.
All containers running code are based on these images, so the updates are picked up on the next build/deploy.
I wouldn't say that's true. We're transitioning into multiple languages, and want to have an environment that will allow future languages to be added as required. Building a generic infrastructure to run containers lets us run everything on the same base platform. Otherwise, we'd need to tailor the images and configuration for the individual language type. When a new language is introduced, it can take 'days or months' to get everything working well.
That's not to say Docker doesn't require the same attention to security as other options. This seems to me akin to running a downloaded base VM image without first doing updates.