openstack-keystone-oshelm

packaged by Chainguard

Chainguard Container for openstack-keystone-oshelm

Minimal OpenStack Identity (Keystone) image compatible with the upstream openstack-helm keystone 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-keystone-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

cgr.dev/ORGANIZATION/openstack-keystone-oshelm is a minimal, distroless drop-in for quay.io/airshipit/keystone, the image the openstack-helm keystone chart targets by default. It needs no chart values overrides beyond the image tags themselves.

Unlike upstream, which sets no User and relies on Apache dropping privileges, this image runs as UID 42424. The chart's pod securityContext sets runAsUser: 42424 either way, so both behave identically when deployed; ours also runs correctly outside the chart. mod_wsgi resolves WSGIDaemonProcess user=keystone by name and chdirs each daemon process into that account's home directory, so the keystone account exists with that UID and a real /var/lib/keystone.

The service lives in a release-scoped virtualenv exposed at /var/lib/openstack, with /var/lib/openstack/bin first on PATH. That is load-bearing rather than cosmetic: the charts invoke bare keystone-manage, openstack and python, and embedded CPython resolves its program name off PATH onto the venv interpreter.

The keystone chart fronts the API with Apache and mod_wsgi, and this image satisfies that contract as shipped:

• apache2 starts and stops with the config the image ships, so both apache2 -DFOREGROUND and the chart's preStop apache2 -k graceful-stop work.
• conf.software.apache2.conf_dir and mods_dir keep their chart defaults — /etc/apache2/conf-enabled and /etc/apache2/mods-available resolve to the directory the shipped config includes, so the chart's wsgi-keystone.conf, security.conf and mpm_event.conf are picked up as-is.
• mod_wsgi is loaded and pointed at the venv, so the chart's stock wsgi.py imports keystone without further configuration.

The a2enmod / a2dismod helpers are not present; leave conf.software.apache2.a2enmod and a2dismod unset (their chart defaults). /etc/apache2/ports.conf is also absent, because the chart's own vhost sets Listen.

The image stream tracks the OpenStack release cycle (e.g. 2026.1 Gazpacho) and corresponds to the openstack-keystone-<stream> apk package group. For kolla-ansible / kayobe deployments use the openstack-keystone-kolla images instead; those serve keystone through uwsgi and follow kolla's kolla_start contract rather than openstack-helm's.

Getting Started

Point the chart's keystone image slots at this image and give the chart registry credentials for cgr.dev (a pull token). The chart attaches imagePullSecrets to its pods only when endpoints.oci_image_registry.auth.enabled is set. Create an override file:

cat > keystone-images.yaml <<EOF
endpoints:
  oci_image_registry:
    auth:
      enabled: true
      keystone:
        username: <pull-token-username>
        password: <pull-token-password>
    host_fqdn_override:
      default: cgr.dev
images:
  tags:
    keystone_api: cgr.dev/ORGANIZATION/openstack-keystone-oshelm:2026.1
    keystone_db_sync: cgr.dev/ORGANIZATION/openstack-keystone-oshelm:2026.1
    keystone_fernet_setup: cgr.dev/ORGANIZATION/openstack-keystone-oshelm:2026.1
    keystone_fernet_rotate: cgr.dev/ORGANIZATION/openstack-keystone-oshelm:2026.1
    keystone_credential_setup: cgr.dev/ORGANIZATION/openstack-keystone-oshelm:2026.1
    keystone_credential_rotate: cgr.dev/ORGANIZATION/openstack-keystone-oshelm:2026.1
    keystone_domain_manage: cgr.dev/ORGANIZATION/openstack-keystone-oshelm:2026.1
EOF

Then install the chart from the openstack-helm repository:

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

The remaining slots (bootstrap, db_init, db_drop, ks_user, keystone_credential_cleanup) run openstack-client, not keystone, and are left to the chart.

Configuration

Configuration comes from the chart, which renders keystone.conf and mounts it at /etc/keystone/. See the openstack-helm keystone chart and the upstream keystone configuration reference for the full set of options.

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.