Also, not every org has (or would want) to go 100% 'all in' on containers. Any hybrid infrastructure will always need configuration management tools like Ansible, Chef or Salt.
- self healing - automatic failover - Docker centric tools
You can have a python s*it show where you use containers like processes. In fact they are processes that probably can't handle signals or pipes. Maybe use tini and that at least works, but it misses the point. Ansible and docker are fundamentally at odds.
When ansible was created it had the promise of a simple layer of abstraction over ssh. now It just does all the things because it jelly. Don't give into the h8
http://docs.ansible.com/ansible/latest/docker_container_modu...
Ansible fits all the automation gaps that exist between all the different infrastructure tools.
I've had issues or a lack of features with ansible's docker support, but use it otherwise for pretty much everything.
I just don't see a point to moving to a wrapper than can never have all the latest support / options that upstream has.
The nice thing about using Ansible for all the management is consistency (especially in mixed container / not-container environments). The nice thing about templating a compose file is being able to track the latest Docker / Compose versions more easily.
a tool for guys that setup your docker, k8s and Swarm.