What's the point of docker connection?

[Joaquin Menchaca]

I was wondering, as docker seems to be more popular to administer servers, not local development systems, what is the point of docker connection?  It's utility seems rather limited.

The docker connection only works on localhost, not on with the docker deamon running on the remote target system you are configuring.  

Thus it is useful to configure the current system you are on, but not so much for a remote system.  You could remotely run an ansible script that works with containers on that system, or do some fancy ssh tunnel, but it is easier to just use command or shell and run `docker exec`.  

Thoughts?

[Matt Martz]

The docker connection implements docker exec and docker cp.  it does work with remote docker servers but does require that the daemon be exposed.

See http://docs.ansible.com/ansible/intro_inventory.html#non-ssh-connection-types

--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscribe@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/050590d6-0ae6-4c22-8469-6437d1b70dcf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Matt Martz
@sivel
sivel.net

[Joaquin Menchaca]

I went by the line: This connector deploys the playbook directly into Docker containers using the local Docker client. I would have liked to use the client from the remote system within the ssh session.

Does exposing a deamon with root access external systems sound like a reasonable solution?  That feels scary.