openstack-barbican-oshelm

packaged by Chainguard

Chainguard Container for openstack-barbican-oshelm

Minimal OpenStack Barbican image compatible with the upstream openstack-helm barbican 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-barbican-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, distroless OpenStack Barbican image for openstack-helm, compatible with the upstream airshipit/barbican image the barbican chart targets by default.

• The image runs as the barbican account (uid/gid 42424, home /var/lib/barbican) by default, where the upstream image runs as root. This matches the chart's runAsUser for the API. The db-sync job sets none, so it runs as barbican rather than root, and chart deployments are unaffected.
• One image serves both barbican slots the chart uses: the barbican-api Deployment (the Key Manager API under uwsgi) and the db-sync job, including the simple crypto KEK rewrap step it runs whenever a KEK is set.
• The service lives in a release-scoped virtualenv and is exposed at /var/lib/openstack, with /var/lib/openstack/bin first on PATH. This is the layout the chart assumes when it invokes bare uwsgi, barbican-db-manage, and python.
• sudo is not included. The upstream image ships it, but the chart does not use it.

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

Prerequisites

The chart needs MariaDB, RabbitMQ, Memcached, and Keystone running before it is installed. See the openstack-helm installation guide.

Getting Started

Point both barbican image slots of the chart at this image and set a key encryption key (KEK) with a values.yaml:

images:
  tags:
    barbican_api: cgr.dev/ORGANIZATION/openstack-barbican-oshelm:2026.1
    barbican_db_sync: cgr.dev/ORGANIZATION/openstack-barbican-oshelm:2026.1
conf:
  barbican:
    simple_crypto_plugin:
      # Generate with: python3 -c 'import base64, os; print(base64.urlsafe_b64encode(os.urandom(32)).decode())'
      kek: "<32-byte url-safe base64 Fernet key>"

Then install the chart from the openstack-helm repository:

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

The chart's other image slots (the database, keystone, and bootstrap jobs, and the helm test) use the openstack-client image, and the RabbitMQ init job uses the rabbitmq image; they are unaffected.

Configuration

Configuration comes from the chart, which renders barbican.conf, the paste pipeline, and the uwsgi configuration and mounts them under /etc/barbican/. Barbican stores secrets with the simple crypto plugin by default.

Since 2025.2 Barbican has no built-in key encryption key, and the chart sets none, so conf.barbican.simple_crypto_plugin.kek is required: without it every secret store fails with a 500 error.

To rotate the key, put the previous key in conf.simple_crypto_kek_rewrap.old_kek, and the db-sync job rewraps the existing project keys. See the openstack-helm barbican chart and the upstream Barbican configuration reference for the full set of options.

Documentation and Resources

• OpenStack Barbican documentation
• openstack-helm documentation
• openstack-helm barbican chart
• Upstream airshipit/barbican 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.