openstack-glance-oshelm

packaged by Chainguard

Chainguard Container for openstack-glance-oshelm

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

• The image runs as the glance account (uid/gid 42424, home /var/lib/glance) by default, where the upstream image runs as root. This matches the chart's runAsUser; the chart still runs the glance-api pod's permission and Ceph keyring init containers as root, so chart deployments are unaffected.
• One image serves every glance workload the chart deploys: the glance-api Deployment (the Image API under uwsgi) and its init containers, and the db-sync and metadefs-load jobs.
• The service 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 invokes bare uwsgi, glance-manage, and glance-rootwrap. The metadata definitions the metadefs-load job reads are at /var/lib/openstack/etc/glance/metadefs.
• The file, HTTP, Ceph RBD, Swift, S3, Cinder, and VMware image stores are included. The Ceph RBD store uses the Ceph 19 client libraries and Python bindings, and the Ceph client tools (ceph, rbd) are included; the upstream image ships Ceph 20.
• sudo is included, so the chart's glance_sudoers rule and rootwrap.conf work unchanged for the Cinder image store's privileged operations.
• The Image API is served by uwsgi only; the chart does not use Apache.

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

Getting Started

Point every glance image slot of the chart at this image with a values.yaml like this:

images:
  tags:
    glance_api: cgr.dev/ORGANIZATION/openstack-glance-oshelm:2026.1
    glance_db_sync: cgr.dev/ORGANIZATION/openstack-glance-oshelm:2026.1
    glance_metadefs_load: cgr.dev/ORGANIZATION/openstack-glance-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 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 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, swift or radosgw for object storage, and cinder for Cinder volumes. 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
• Upstream airshipit/glance 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.