Molecule container image with docker and podman support
10K+
Container image with Molecule and Molecule plugins, built on top of gwerlas/ansible.
GitLab Project : yoanncolin/container-images/molecule.
Every tag moves to the newest matching build, X.Y.Z included: the image of
the current version is rebuilt weekly for security updates. To keep an image
fixed, pin its digest (gwerlas/molecule@sha256:…) in docker pull or FROM.
latest runs the ansible-core of gwerlas/ansible:14 (2.21). A flavour on the
oldest ansible-core the gwerlas.system collection supports carries the same
tags with a -coreX.Y suffix (26.10.0-core2.19, 26.10-core2.19, …), and
coreX.Y in place of latest :
| Version | Tags | Rebuild | Source |
|---|---|---|---|
| 26.11.0 | 26.11.0, 26.11, 26, latest | Weekly | Dockerfile |
| 26.11.0-core2.19 | 26.11.0-core2.19, 26.11-core2.19, 26-core2.19, core2.19 | Weekly | Dockerfile |
| 26.10.0 | 26.10.0, 26.10 | Dockerfile | |
| 26.10.0-core2.19 | 26.10.0-core2.19, 26.10-core2.19 | Dockerfile | |
| 26.9.0 | 26.9.0, 26.9 | Dockerfile | |
| 26.8.0 | 26.8.0, 26.8 | Dockerfile | |
| 26.6.0 | 26.6.0, 26.6 | Dockerfile | |
| 26.4.0 | 26.4.0, 26.4 | Dockerfile | |
| 26.3.0 | 26.3.0, 26.3 | Dockerfile | |
| 26.2.0 | 26.2.0, 26.2 | Dockerfile | |
| 25.12.0 | 25.12.0, 25.12, 25 | Dockerfile | |
| 25.11.1 | 25.11.1, 25.11 | Dockerfile | |
| 25.11.0 | 25.11.0 | Dockerfile | |
| 25.9.0 | 25.9.0, 25.9 | Dockerfile | |
| 25.4.0 | 25.4.0, 25.4 | Dockerfile | |
| 25.3.1 | 25.3.1, 25.3 | Dockerfile | |
| 25.2.0 | 25.2.0, 25.2 | Dockerfile | |
| 24.12.0 | 24.12.0, 24.12, 24 | Dockerfile | |
| 24.2.1 | 24.2.1, 24.2 | Dockerfile | |
| 24.2.0 | 24.2.0 | Dockerfile | |
| 6.0.3 | 6.0.3, 6.0, 6 | Dockerfile | |
| 6.0.2 | 6.0.2 | Dockerfile | |
| 6.0.1 | 6.0.1 | Dockerfile | |
| 6.0.0 | 6.0.0 | Dockerfile | |
| 5.1.0 | 5.1.0, 5.1, 5 | Dockerfile | |
| 5.0.1 | 5.0.1, 5.0 | Dockerfile | |
| 5.0.0 | 5.0.0 | Dockerfile | |
| 4.0.4 | 4.0.4, 4.0, 4 | Dockerfile |
You'll need to have a configured and running libvirt for virtual machines based tests scenarios.
You'll need to have a configured container engine (Docker or Podman) for containers based tests scenarios.
The container runs as the build user (non-root) inherited from the
gwerlas/ansible image. When mounting a local directory, make sure it
is readable and writable by that user, or pass your own UID/GID.
docker run -t --rm \
-v $HOME/.ansible:/home/build/.ansible \
-v $PWD:$PWD \
-w $PWD \
-v /run/docker.sock:/run/docker.sock \
gwerlas/molecule \
molecule test
For virtual machines, use Molecule's default driver: its create.yml and
destroy.yml playbooks drive libvirt from Ansible (with community.libvirt,
shipped in the image), through the host's libvirt socket :
Breaking: Vagrant is no longer shipped. The
vagrantcommand, thevagrant-libvirtplugin and Molecule'svagrantdriver are gone, along with the Debian unstable packages they came from. Move VM-based scenarios to thedefaultdriver, or pin an older tag meanwhile.
docker run -t --rm \
-v $HOME/.ansible:/home/build/.ansible \
-v $PWD:$PWD \
-w $PWD \
--cap-add SYS_ADMIN \
--cap-add NET_ADMIN \
-v /run/libvirt:/run/libvirt \
-v /var/lib/libvirt:/var/lib/libvirt \
gwerlas/molecule \
molecule test
Content type
Image
Digest
sha256:db20da8f2…
Size
345.3 MB
Last updated
3 days ago
docker pull gwerlas/molecule