Skip to content

Latest commit

 

History

History
43 lines (27 loc) · 2.82 KB

README.md

File metadata and controls

43 lines (27 loc) · 2.82 KB
Raw

Ubuntu 20.04 LTS (Focal Fossa) Ansible Test Image

FORK REASON: This image was forked from geerlingguy/docker-ubuntu2004-ansible, to add a normal user with sudo privileges, because that is the type of user as which I normally connect to servers with Ansible.

Build Docker pulls

Ubuntu 20.04 LTS (Focal Fossa) Docker container for Ansible playbook and role testing.

Tags

  • latest: Latest stable version of Ansible.

The latest tag is a lightweight image for basic validation of Ansible playbooks.

How to Build

This image is built on Docker Hub automatically any time the upstream OS container is rebuilt, and any time a commit is made or merged to the master branch. But if you need to build the image on your own locally, do the following:

  1. Install Docker.
  2. cd into this directory.
  3. Run docker build -t ubuntu2004-ansible .

How to Use

  1. Install Docker.
  2. Pull this image from Docker Hub: docker pull geoffreyvanwyk/docker-ubuntu2004-ansible:latest (or use the image you built earlier, e.g. ubuntu2004-ansible:latest).
  3. Run a container from the image: docker run --detach --privileged --volume=/sys/fs/cgroup:/sys/fs/cgroup:rw --cgroupns=host geoffreyvanwyk/docker-ubuntu2004-ansible:latest (to test my Ansible roles, I add in a volume mounted from the current working directory with --volume=`pwd`:/etc/ansible/roles/role_under_test:ro).
  4. Use Ansible inside the container: a. docker exec --tty [container_id] env TERM=xterm ansible --version b. docker exec --tty [container_id] env TERM=xterm ansible-playbook /path/to/ansible/playbook.yml --syntax-check

Notes

I use Docker to test my Ansible roles and playbooks on multiple OSes using CI tools like Jenkins and Travis. This container allows me to test roles and playbooks using Ansible running locally inside the container.

Important Note: I use this image for testing in an isolated environment—not for production—and the settings and configuration used may not be suitable for a secure and performant production environment. Use on production servers/in the wild at your own risk!

Author