No description
  • Dockerfile 88.4%
  • Python 11.6%
Find a file
Matt Clay 48de6d3bfb
Add libicu to Fedora (#132)
This will allow PowerShell to be used.
2026-02-18 11:47:06 -08:00
containers Add libicu to Fedora (#132) 2026-02-18 11:47:06 -08:00
azure-pipelines.py Implement new container versioning scheme (#125) 2025-08-28 16:28:08 -07:00
azure-pipelines.yml Miscellaneous updates (#128) 2025-09-10 16:44:04 -07:00
build.yml Implement new container versioning scheme (#125) 2025-08-28 16:28:08 -07:00
install.yml Use containmint==0.2.0 from PyPI. (#91) 2022-06-21 12:56:08 -07:00
LICENSE Initial commit 2018-08-16 12:00:01 -07:00
README.md Implement new container versioning scheme (#125) 2025-08-28 16:28:08 -07:00

distro-test-containers

Distribution specific containers for Ansible testing.

Directory Structure

Each directory under containers corresponds to a quay.io repository. The suffix -test-container is appended to each directory name to derive the repository name.

Within each directory is one or more version subdirectories. Each version becomes the first component of the container tag. The branch name or release version becomes the second component of the container tag.

This results in container and tag names of the form:

{container_name}-test-container:{container_version}-{branch_or_release_version}

NOTE: Prior to ansible-core 2.20, a different container naming and tagging scheme was used.

Branch Names

The primary development branch is the main branch. Additionally, there are stable-X.Y branches for each associated ansible-core release.

Release Names

Release names are of the form vX.Y-N. The X.Y component corresponds to the associated ansible-core release. The N component is incremented with each container release for the same ansible-core release, starting from zero.

NOTE: Prior to ansible-core 2.20, a different release versioning scheme was used.

Default Container

If you are looking for the default test container then see: