openstack-manila-oshelm

packaged by Chainguard

Chainguard Container for openstack-manila-oshelm

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

• The image runs as the manila account (uid/gid 42424, home /var/lib/manila) by default, where the upstream image runs as root. This matches the chart's runAsUser, so chart deployments are unaffected.
• One image serves every manila workload the chart deploys: the manila-api Deployment (the Shared File Systems API under uwsgi), manila-scheduler, manila-share, manila-data, the db-sync job, and the db-purge CronJob.
• 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, manila-*, and manila-rootwrap.
• sudo is included, so the chart's manila_sudoers rule and rootwrap.conf work unchanged for the privileged operations of manila-share.
• The CephFS driver (native CephFS and NFS through NFS-Ganesha) uses the Ceph 20 client libraries and Python bindings. NFS client tools (mount.nfs) are not included, as in the upstream image.
• GNU coreutils and hostname are included for manila-data's copy helper and the share pod's hostname --fqdn init step.

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

Getting Started

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

images:
  tags:
    manila_db_sync: cgr.dev/ORGANIZATION/openstack-manila-oshelm:2026.1
    manila_api: cgr.dev/ORGANIZATION/openstack-manila-oshelm:2026.1
    manila_data: cgr.dev/ORGANIZATION/openstack-manila-oshelm:2026.1
    manila_scheduler: cgr.dev/ORGANIZATION/openstack-manila-oshelm:2026.1
    manila_share: cgr.dev/ORGANIZATION/openstack-manila-oshelm:2026.1
    manila_db_purge: cgr.dev/ORGANIZATION/openstack-manila-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 manila openstack-helm/manila --namespace openstack --values values.yaml

The chart's database, keystone, and bootstrap jobs use the openstack-client image, and its dependency-check and RabbitMQ init containers use their own images; all are unaffected.

Configuration

Configuration comes from the chart, which renders manila.conf, the backend configuration, rootwrap.conf, the uwsgi configuration, and the sudoers rule, and mounts them under /etc/manila/ and /etc/sudoers.d/. The chart's default backend is the generic driver, which needs a Nova service image; openstack-helm's own manila job configures the CephFS driver over NFS-Ganesha instead. See the openstack-helm manila chart and the upstream manila configuration reference for the full set of options.

Documentation and Resources

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