openstack-kolla-toolbox-fips

packaged by Chainguard

Chainguard Container for openstack-kolla-toolbox-fips

FIPS variant of openstack-kolla-toolbox — same image, built against FIPS-validated OpenSSL.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/openstack-kolla-toolbox-fips:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

The openstack-kolla-toolbox-fips image is a minimal, distroless drop-in replacement for the upstream openstack.kolla/kolla-toolbox image, compatible with kolla-ansible and kayobe. It is not an OpenStack service daemon but kolla-ansible's deployment "swiss-army-knife": kolla-ansible execs into it (docker exec kolla_toolbox ...) to run ansible modules and OpenStack client commands against a cluster. It bundles a Python venv at /opt/ansible containing ansible-core, ansible-runner, openstacksdk, python-openstackclient and friends, plus the ansible collections kolla-ansible depends on.

As with the upstream image it runs as the unprivileged ansible user (uid/gid 42401, a member of the kolla group), and shares the kolla startup contract: /usr/local/bin/kolla_start reads /var/lib/kolla/config_files/config.json, runs kolla_set_configs, then dispatches to the configured command. The image stream tracks the OpenStack release cycle (e.g. 2026.1 Gazpacho); each stream corresponds to the openstack-kolla-toolbox-<stream>-fips apk package and pins ansible-core + the client stack to the versions kolla ships for that release.

FIPS Support

The openstack-kolla-toolbox-fips Chainguard Container ships with a validated redistribution of the OpenSSL's FIPS provider module. Every crypto entry point routes through the FIPS-validated system OpenSSL rather than a bundled copy: CPython's stdlib (ssl, hashlib) already links the system OpenSSL; the venv-local PyPI cryptography wheel (which statically bundles its own non-FIPS OpenSSL) is dropped at build time so import cryptography falls through to the py3.XX-cryptography apk built against the system OpenSSL, and openssl-config-fipshardened activates the FIPS provider. For more on FIPS support in Chainguard Containers, consult the guide on FIPS-enabled Chainguard Containers on Chainguard Academy.

Getting Started

In a normal deployment you do not run this image directly — kolla-ansible substitutes it as the kolla_toolbox container and drives it for you. Configuration is supplied via kolla's config.json mechanism and by kolla-ansible itself; see the upstream kolla-ansible documentation for the canonical deployment workflow.

For those with access, the container image is available on cgr.dev and can also be exercised standalone:

docker pull cgr.dev/ORGANIZATION/openstack-kolla-toolbox-fips:latest
docker run --rm --entrypoint openstack cgr.dev/ORGANIZATION/openstack-kolla-toolbox-fips:latest --version

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Documentation and Resources

• kolla-ansible documentation
• Upstream kolla-toolbox image
• python-openstackclient documentation

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.