openstack-client-oshelm

packaged by Chainguard

Chainguard Container for openstack-client-oshelm

Minimal OpenStack client image compatible with the upstream openstack-helm openstack-client 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-client-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-client-oshelm is a minimal drop-in for quay.io/airshipit/openstack-client, the image openstack-helm charts run for their bootstrap, db-init, db-drop, ks-user, ks-service and ks-endpoints jobs. openstack-helm's host openstack wrapper also runs it with docker run.

The client and its plugins live in a release-scoped virtualenv exposed at /var/lib/openstack, with /var/lib/openstack/bin first on PATH. The chart jobs rely on this layout when they run bare openstack or #!/usr/bin/env python scripts.

• The image runs as root by default, like the upstream image. Most chart jobs set no runAsUser, and the host wrapper writes files into bind-mounted host directories.
• The openstackclient account is uid/gid 42424, and /etc/openstackclient, /var/lib/openstackclient, /var/log/openstackclient and /var/cache/openstackclient are owned by it.
• The virtualenv carries the same client plugins and console scripts (openstack, nova, glance, cinder, heat, swift, uwsgi and others), plus sqlalchemy and pymysql for the database jobs. bash, curl and jq are included.
• Unlike the upstream image, this image does not include git, wget, sudo, patch, gnupg, host or a system /usr/bin/python3 (use python3 from PATH), nor upstream's /etc/image_info build metadata. The chart jobs don't use any of these.

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

Getting Started

Point a chart's openstack-client image slots at this image, for example in the keystone chart values:

images:
  tags:
    bootstrap: cgr.dev/ORGANIZATION/openstack-client-oshelm:2026.1
    db_init: cgr.dev/ORGANIZATION/openstack-client-oshelm:2026.1
    db_drop: cgr.dev/ORGANIZATION/openstack-client-oshelm:2026.1
    ks_user: cgr.dev/ORGANIZATION/openstack-client-oshelm:2026.1

Configuration

The charts supply every command, credential and configuration file. See the openstack-helm documentation and the python-openstackclient documentation for details.

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.