openstack-horizon-kolla-fips

packaged by Chainguard

Chainguard Container for openstack-horizon-kolla-fips

FIPS variant of openstack-horizon-kolla — 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-horizon-kolla-fips:latest

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

openstack-horizon-kolla-fips

FIPS variant of openstack-horizon-kolla. Same image, built against FIPS-validated OpenSSL with openssl-config-fipshardened loaded by default. It is a drop-in replacement for the upstream kolla/horizon image when consumed by kolla-ansible or kayobe, with the FIPS provider activated and all crypto operations routed through FIPS-validated primitives.

The image follows 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 (typically uwsgi serving the Horizon WSGI application).

OpenStack release streams

The image tracks the OpenStack release cycle and ships one stream per supported release. The stream name (e.g. 2026.1) is embedded in the apk package name (openstack-horizon-<release>-fips) and pins to the matching horizon release series. See the OpenStack releases page for the codename and support status of each release.

Configuration

Configuration is supplied via kolla's config.json mechanism — see the upstream kolla-ansible horizon role for the canonical examples. Refer to the upstream horizon configuration reference for the full set of options.

FIPS Support

This is the FIPS-enabled variant of the Chainguard openstack-horizon-kolla image. It includes openssl-config-fipshardened, which configures OpenSSL to run in FIPS mode so that all cryptographic operations — including the Django secret-key store, session/CSRF token handling, and TLS connections to Keystone and other OpenStack services — are routed through FIPS-validated primitives. Non-FIPS algorithms such as MD5 and RC4 are disabled at the OpenSSL library level.

For general usage instructions, see the non-FIPS openstack-horizon-kolla image. For more on FIPS support in Chainguard Containers, consult the guide on FIPS-enabled Chainguard Containers on Chainguard Academy.

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.