openstack-nova-oshelm

packaged by Chainguard

Chainguard Container for openstack-nova-oshelm

Minimal OpenStack Compute (Nova) image compatible with the upstream openstack-helm nova 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-nova-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 Compute (Nova) image for openstack-helm, compatible with the upstream airshipit/nova image the nova chart targets by default.

One image serves every nova pod the chart deploys: the API and metadata API (both under uwsgi), conductor, scheduler, the noVNC and SPICE console proxies, the database jobs, and the privileged nova-compute DaemonSet with its SSH sidecar for migrations.

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 nova-*, nova-manage, uwsgi and python.

• The nova account is uid/gid 42424 with its home at /var/lib/nova, and the image runs as that user by default, matching the chart's runAsUser. The tss account (42434) is present for vTPM guests.
• sudo is included so nova-compute can escalate through the chart's nova-rootwrap sudoers entry.
• The noVNC web assets are available at /usr/share/novnc (with vnc_auto.html) and the SPICE assets at /usr/share/spice-html5, where the chart's console proxy init containers copy them from.
• Ceph (RBD) client libraries and CLI, the libvirt Python bindings, Open vSwitch bindings, qemu-img and genisoimage (for config drives) are included.
• OpenSSH 10 no longer supports DSA keys. When enabling the chart's SSH sidecar (network.ssh.enabled), drop dsa from network.ssh.key_types (the chart default is rsa and dsa).

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

Getting Started

Point every nova image slot of the chart at this image. Starting from upstream's values_overrides/nova/2026.1-ubuntu_noble.yaml, a values.yaml looks like this:

images:
  tags:
    nova_api: cgr.dev/ORGANIZATION/openstack-nova-oshelm:2026.1
    nova_cell_setup: cgr.dev/ORGANIZATION/openstack-nova-oshelm:2026.1
    nova_compute: cgr.dev/ORGANIZATION/openstack-nova-oshelm:2026.1
    nova_compute_ssh: cgr.dev/ORGANIZATION/openstack-nova-oshelm:2026.1
    nova_conductor: cgr.dev/ORGANIZATION/openstack-nova-oshelm:2026.1
    nova_db_sync: cgr.dev/ORGANIZATION/openstack-nova-oshelm:2026.1
    nova_novncproxy: cgr.dev/ORGANIZATION/openstack-nova-oshelm:2026.1
    nova_novncproxy_assets: cgr.dev/ORGANIZATION/openstack-nova-oshelm:2026.1
    nova_scheduler: cgr.dev/ORGANIZATION/openstack-nova-oshelm:2026.1
    nova_spiceproxy: cgr.dev/ORGANIZATION/openstack-nova-oshelm:2026.1
    nova_spiceproxy_assets: cgr.dev/ORGANIZATION/openstack-nova-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 nova openstack-helm/nova --namespace openstack --values values.yaml

The chart's other image slots (the bootstrap, database and keystone jobs, and the service cleaner) use the openstack-client and ceph-config-helper images and are unaffected.

Configuration

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

Documentation and Resources

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