openstack-glance-oshelm-fips

packaged by Chainguard

Chainguard Container for openstack-glance-oshelm-fips

FIPS variant of openstack-glance-oshelm, 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-glance-oshelm-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

cgr.dev/ORGANIZATION/openstack-glance-oshelm-fips is the FIPS variant of openstack-glance-oshelm, a minimal, distroless drop-in for quay.io/airshipit/glance, the image the openstack-helm glance chart targets by default. It follows the same chart contract: it runs as UID 42424, serves every glance workload the chart deploys (the glance-api Deployment under uwsgi and its init containers, and the db-sync and metadefs-load jobs), includes sudo for the Cinder image store's glance-rootwrap rule, and exposes the service virtualenv at /var/lib/openstack with /var/lib/openstack/bin first on PATH. See the openstack-glance-oshelm documentation for the details of that contract.

The image stream tracks the OpenStack 2026.1 (Gazpacho) release and corresponds to the openstack-glance-2026.1-fips apk package group.

Compared with openstack-glance-oshelm, the image hash (hashing_algorithm) accepts only SHA-2 and SHA-3 values (default sha512), and adding a location with validation_data accepts only sha256 or sha512. Glance still computes the legacy MD5 checksum through the OpenSSL legacy provider, which the image enables; with CHAINGUARD_LEGACY_ALLOWED=0, image uploads fail. MariaDB ed25519_password authentication and oslo.middleware HTTP basic authentication are not supported.

FIPS Support

The openstack-glance-oshelm-fips Chainguard Container ships with a validated redistribution of OpenSSL's FIPS provider module. For more on FIPS support in Chainguard Containers, consult the guide on FIPS-enabled Chainguard Containers on Chainguard Academy.

Prerequisites

Glance needs Keystone, MariaDB, and RabbitMQ, plus an image store. The chart's storage value defaults to swift, and glance-api waits for the storage-init job, so either deploy Swift (or radosgw) or set storage in values.yaml to a backend you have, such as pvc or rbd. Use FIPS variants of those services where they exist. See upstream's deploy-compute-kit.yaml playbook for a full deployment.

Getting Started

Point every glance image slot of the chart at this image and give the chart registry credentials for cgr.dev (a pull token). To have the chart create and attach the registry Secret shown below, enable endpoints.oci_image_registry.auth.enabled. Create a values.yaml:

cat > values.yaml <<EOF
endpoints:
  oci_image_registry:
    auth:
      enabled: true
      glance:
        username: <pull-token-username>
        password: <pull-token-password>
    host_fqdn_override:
      default: cgr.dev
images:
  tags:
    glance_api: cgr.dev/ORGANIZATION/openstack-glance-oshelm-fips:2026.1
    glance_db_sync: cgr.dev/ORGANIZATION/openstack-glance-oshelm-fips:2026.1
    glance_metadefs_load: cgr.dev/ORGANIZATION/openstack-glance-oshelm-fips: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 glance openstack-helm/glance --namespace openstack --values values.yaml

The chart's other image slots (the database, keystone, bootstrap, and Ceph storage-init jobs) use the openstack-client and ceph-config-helper images, the RabbitMQ init job uses the rabbitmq image, and the dependency-check init containers, Rally test pod, and image sync job use their own images. With storage set to rbd or radosgw, the storage-init job's ceph-keyring-placement init container uses the glance_api slot, so it runs this image.

Configuration

Configuration comes from the chart, which renders glance-api.conf, the paste pipeline, the policy, the uwsgi configuration, rootwrap.conf, and the sudoers rule, and mounts them under /etc/glance/ and /etc/sudoers.d/. The chart's storage value selects the image store: pvc or local for the file store, rbd for Ceph, and swift or radosgw for object storage. storage: cinder only adds the pod settings the Cinder store needs and still renders the file backend on an emptyDir, so for Cinder also set conf.glance.DEFAULT.enabled_backends, conf.glance.glance_store.default_backend, and a Cinder backend section. See the openstack-helm glance chart and the upstream glance configuration reference for the full set of options.

Documentation and Resources

• OpenStack Glance documentation
• openstack-helm documentation
• openstack-helm glance chart
• FIPS-enabled Chainguard Containers

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.