openstack-horizon-oshelm

packaged by Chainguard

Chainguard Container for openstack-horizon-oshelm

Minimal OpenStack Horizon image compatible with the upstream openstack-helm horizon image.

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-oshelm:latest

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

Compatibility Notes

Minimal OpenStack Horizon image for openstack-helm, compatible with the upstream airshipit/horizon image the horizon chart targets by default.

• The image runs as the horizon account (uid/gid 42424, home /var/lib/horizon) by default, where the upstream image runs as root. The chart runs the horizon Deployment and the db-sync job as root, and Apache's mod_wsgi daemon processes drop to horizon, so chart deployments are unaffected.
• One image serves both workloads the chart deploys: the horizon Deployment (the dashboard under Apache and mod_wsgi) and the db-sync job.
• The dashboard lives in a release-scoped virtualenv and is exposed at /var/lib/openstack, with /var/lib/openstack/bin first on PATH, the layout the chart assumes when it runs bare python and manage.py.
• Apache is the upstream httpd build with a Debian-style layout on top: apache2 (which the chart starts with -DFOREGROUND and stops with -k graceful-stop), a2enmod and a2dismod, /etc/apache2/envvars, and sites-available and conf-available directories that receive the chart's vhost and security.conf. The base configuration listens on port 80.
• gettext is included, so the chart compiles message catalogs at startup.
• The upstream image ships no plugin dashboards; this image adds the ones Kolla's horizon image ships, including heat_dashboard, so the chart's default extra_panels enables the Heat panel. neutron_taas_dashboard, also in that default list, is not included; the chart skips panels that are not installed.

Each image stream tracks the OpenStack release cycle (e.g. 2026.1 Gazpacho) and corresponds to the openstack-horizon-<stream> apk package group.

Getting Started

Point the chart's horizon image slots at this image:

images:
  tags:
    horizon: cgr.dev/ORGANIZATION/openstack-horizon-oshelm:2026.1
    horizon_db_sync: cgr.dev/ORGANIZATION/openstack-horizon-oshelm:2026.1

Then install the chart from the openstack-helm repository:

helm repo add openstack-helm https://tarballs.opendev.org/openstack/openstack-helm
helm upgrade --install horizon openstack-helm/horizon --namespace openstack --values values.yaml

The chart's other image slots (the database init and drop jobs, the helm test, and the dependency checks) use the openstack-client, osh-selenium, and kubernetes-entrypoint images and are unaffected.

Configuration

Configuration comes from the chart, which renders local_settings into /etc/openstack-dashboard/, the Apache vhost and security.conf, and the horizon.sh, manage.py and django.wsgi scripts. By default the chart uses memcached for caching and sessions, MariaDB for the database, and keystone's internal endpoint for authentication. See the openstack-helm horizon chart and the upstream horizon settings reference for the full set of options.

Documentation and Resources

• OpenStack Horizon documentation
• openstack-helm documentation
• openstack-helm horizon chart
• Upstream airshipit/horizon Dockerfile

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.