A Docker image with Ansible and an SSH server.
latest,2.1.0.02.0.2.02.0.0.2
You can't do much with Ansible unless you can access your servers. For that, you need your SSH keys to be loaded in an ssh-agent accessible within the container. The easiest way to do that is to use your local ssh-agent, and SSH into the container with agent forwarding enabled.
The solita/ansible-ssh base image contains a user called ansible, but does not allow anyone to log in. Use a Dockerfile such as the following to create an image that allows logging in as ansible with your SSH keys (assuming that you have copied your public key id_rsa.pub to the same directory as the Dockerfile).
FROM solita/ansible-ssh
COPY id_rsa.pub /tmp/
RUN cat /tmp/id_rsa.pub >> /home/ansible/.ssh/authorized_keys && rm -f /tmp/id_rsa.pub
See the sections Configuring the Docker host and Running in the README of solita/ubuntu-systemd, on which this image is based.
Additionally you should forward the container's SSH port 22 to some port, e.g. 2222, on the Docker host. To do that, add the option -p 2222:22 to your docker create or docker run command.
You can SSH into the container as the user ansible. Use the -A switch to enable agent forwarding.
Assuming your Docker host is localhost and you've forwarded the container's port 22 to 2222 on the host, you can connect to the container like this:
ssh \
-o UserKnownHostsFile=/dev/null \
-o StrictHostKeyChecking=no \
-A \
-p 2222 \
ansible@localhost
The -o switches disable host key checking. Without them, SSH will refuse to connect when you use the port 2222 for another container with a different host key. You should only disable host key checking when there is no chance of a man-in-the-middle attack (i.e. only when you're connecting to a container running on the same physical host)!
The -A switch enables agent forwarding.
Copyright © 2016 Solita. Licensed under the MIT license.