Docker-Ansible base images
Repository name in Docker Hub: williamyeh/ansible
These are Docker images for Ansible software, installed in a selected Linux distributions.
OS: Debian (jessie, wheezy), Ubuntu (trusty, precise), CentOS (7, 6), Alpine (3).
Ansible: usually the most recent stable and experimental versions (I didn't pin any specific version).
Images and tags
Stable version (installed from official PyPI repo):
Onbuild series (recommended for common cases):
Experimental version (building directly from the git
master source tree; use at your own risk!):
Onbuild series (recommended for common cases):
For the impatient
Here comes a simplest working example for the impatient.
First, choose a base image you'd like to begin with. For example,
Second, put the following
Dockerfile along with your playbook directory:
FROM williamyeh/ansible:ubuntu14.04-onbuild # ==> Specify requirements filename; default = "requirements.yml" #ENV REQUIREMENTS requirements.yml # ==> Specify playbook filename; default = "playbook.yml" #ENV PLAYBOOK playbook.yml # ==> Specify inventory filename; default = "/etc/ansible/hosts" #ENV INVENTORY inventory.ini # ==> Executing Ansible (with a simple wrapper)... RUN ansible-playbook-wrapper
docker build .
For more advanced usage, the role in Ansible Galaxy
williamyeh/nginx demonstrates how to perform a simple smoke test (configuration needs test, too!) on a variety of (containerized) Linux distributions via CircleCI's Ubuntu 12.04 and Travis CI’s Ubuntu 14.04 worker instances.
Why yet another Ansible image for Docker?
There has been quite a few Ansible images for Docker (e.g., search in the Docker Hub), so why reinvent the wheel?
In the beginning I used the
ansible/ansible-docker-base created by Ansible Inc. It worked well, but left some room for improvement:
Base OS image - It provides only
ubuntu:14.04. Insufficent for me.
Unnecessary dependencies - It installed, at the very beginning of its Dockerfile, the
software-properties-commonpackage, which in turns installed some Python packages. I prefered to incorporate these stuff only when absolutely needed.
Therefore, I built these Docker images on my own.
ansible/ansible-docker-base announced in September 2015: “Ansible no longer maintains images in Dockerhub directly.”
Comparison: image size
REPOSITORY TAG VIRTUAL SIZE --------------------------- ------------------- ------------ ansible/centos7-ansible stable 367.5 MB ansible/ubuntu14.04-ansible stable 286.6 MB williamyeh/ansible alpine3-onbuild 66.4 MB williamyeh/ansible centos6-onbuild 264.2 MB williamyeh/ansible centos7-onbuild 275.3 MB williamyeh/ansible debian7-onbuild 134.4 MB williamyeh/ansible debian8-onbuild 178.3 MB williamyeh/ansible ubuntu12.04-onbuild 181.9 MB williamyeh/ansible ubuntu14.04-onbuild 238.3 MB
Used mostly as a base image for configuring other software stack on some specified Linux distribution(s).
Take Debian/Ubuntu/CentOS for example. To test an Ansible
playbook.yml against a variety of Linux distributions, we may use Vagrant as follows:
# Vagrantfile Vagrant.configure(2) do |config| # ==> Choose a Vagrant box to emulate Linux distribution... config.vm.box = "ubuntu/trusty64" #config.vm.box = "ubuntu/precise64" #config.vm.box = "debian/jessie64" #config.vm.box = "debian/wheezy64" #config.vm.box = "bento/centos-7.2" #config.vm.box = "bento/centos-6.7" #config.vm.box = "maier/alpine-3.3.1-x86_64" # ==> Executing Ansible... config.vm.provision "ansible" do |ansible| ansible.playbook = "playbook.yml" end end
Virtual machines can emulate a variety of Linux distributions with good quality, at the cost of runtime overhead.
Docker to be a rescue. Now, with these williamyeh/ansible series, we may test an Ansible
playbook.yml against a variety of Linux distributions as follows:
# Dockerfile # ==> Choose a base image to emulate Linux distribution... FROM williamyeh/ansible:ubuntu14.04 #FROM williamyeh/ansible:ubuntu12.04 #FROM williamyeh/ansible:debian8 #FROM williamyeh/ansible:debian7 #FROM williamyeh/ansible:centos7 #FROM williamyeh/ansible:centos6 #FROM williamyeh/ansible:alpine3 # ==> Copying Ansible playbook... WORKDIR /tmp COPY . /tmp # ==> Creating inventory file... RUN echo localhost > inventory # ==> Executing Ansible... RUN ansible-playbook -i inventory playbook.yml \ --connection=local --sudo
You may also work with
onbuild series, which take care of many routine steps for you:
# Dockerfile # ==> Choose a base image to emulate Linux distribution... FROM williamyeh/ansible:ubuntu14.04-onbuild #FROM williamyeh/ansible:ubuntu12.04-onbuild #FROM williamyeh/ansible:debian8-onbuild #FROM williamyeh/ansible:debian7-onbuild #FROM williamyeh/ansible:centos7-onbuild #FROM williamyeh/ansible:centos6-onbuild #FROM williamyeh/ansible:alpine3-onbuild # ==> Specify requirements filename; default = "requirements.yml" #ENV REQUIREMENTS requirements.yml # ==> Specify playbook filename; default = "playbook.yml" #ENV PLAYBOOK playbook.yml # ==> Specify inventory filename; default = "/etc/ansible/hosts" #ENV INVENTORY inventory.ini # ==> Executing Ansible (with a simple wrapper)... RUN ansible-playbook-wrapper
With Docker, we can test any Ansible playbook against any version of any Linux distribution without the help of Vagrant. More lightweight, and more portable across IaaS, PaaS, and even CaaS (Container as a Service) providers!
If better OS emulation (virtualization) isn't required, the Docker approach (containerization) should give you a more efficient Ansible experience.
Author: William Yeh email@example.com
Licensed under the Apache License V2.0. See the LICENSE file for details.