Hacker News Reader

Comment by alexnewman | Hacker News Reader

ansible and containers do not mix well. Don't even bother. They take totally different approaches. Use ansible for what it is good for. Using it to automate all the things ... in container world... I mean why have docker-compose or k8s at all. Just launch containers willy nilly and instead of

- 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

View on HN

Ansible works quite well for automating docker deployments. Something still has to execute the docker commands to spin up a container/swarm/cluster/whatever. Better to have those commands be idempotent and checked in to version control.

http://docs.ansible.com/ansible/latest/docker_container_modu...

And if you control networking, Ansible can manage that... and if you control local workstation management, Ansible can manage that... and if you need something to manage things like CloudFormation with automation...

Ansible fits all the automation gaps that exist between all the different infrastructure tools.

I just click the google cluster or Ecs button and choose auto scale . Startups are often wasting time with code as infra.

Would you mind expanding on that please? I'm really curious about the role of configuration management tools in a containerized world.

Managing the setting up the container system of your choice, deployment of those containers, moving yaml around, calling APIs, etc.

Yes they do, and if you're willing to go all in with Ansible you can entirely replace docker-compose.

Why not simply call docker-compose through ansible and template the yml?

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.

I've done it both ways—both are valid approaches.

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.

Reply on news.ycombinator.com