You aren't "missing" anything, you are just doing things differently. Containers are a way of storing code and configurations in a single deployable entity. Le

You aren't "missing" anything, you are just doing things differently. Containers are a way of storing code and configurations in a single deployable entity. Let's say I want to change a services version from 1.2 to 1.3. If I did this in Ansible, I might do it by commanding all of my services to pull the code of version 1.3 from a git repo and restarting to make the change. If I did this with containers, I'd tell them to pull the image version 1.3 from docker registry and after it's pulled to shut down v.1.2 and start v.1.3. Those things just have some smaller differences that are good in terms of A and worse in terms of B. Ansible helps you by keeping it closer to the traditional way of just pushing code changes to a machine and that's that, and Docker opens up this world where the infrastructure can scale up or down (elasticity) quicker horizontally. Kubernetes is just an extrapolation of that elasticity. Ansible is "good enough" if you don't need elasticity or you have programmed another custom solution to handle that. Docker/Kube and Ansible both have Git at their hearts, so if your app components have all they need as code, and you don't worry about elasticity, you won't gain a lot from wrapping it up in a Dockerfile (as opposed to just git cloning).