openstack-ceph-config-helper

packaged by Chainguard

Chainguard Container for openstack-ceph-config-helper

Minimal Ceph and OpenStack client tooling image compatible with the upstream openstack-helm ceph-config-helper 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-ceph-config-helper:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

openstack-ceph-config-helper

Minimal Ceph, Kubernetes and OpenStack client tooling image for openstack-helm, compatible with the upstream airshipit/ceph-config-helper image.

The charts run their own scripts in this image to wire OpenStack services to Ceph: creating RBD pools, placing client keyrings and writing ceph.conf from the cluster's monitor endpoints. It ships the CLIs those scripts call:

• ceph, rbd and rados from Ceph 20
• kubectl
• openstack and swift, pinned to the OpenStack release's upper-constraints
• s3cmd, jq, curl and python3
• bash, with GNU coreutils

Compatibility Notes

The image runs as the nonroot user (uid 65532) unless a chart sets a user; upstream runs as root. In the charts listed under Getting Started, only ceph-adapter-rook's config job keeps the image's default user, and it needs no root: it runs only kubectl and text tools, with no Ceph calls.

Other differences from upstream:

• python3 is Python 3.13 and cannot import the Ceph bindings (rados, rbd), which are built for Python 3.12, or the OpenStack client libraries (openstackclient, swiftclient, rgwadmin), which live in a private virtual environment behind the openstack and swift commands.
• pip is not included.
• awk, sed and grep are provided by busybox, not GNU.

OpenStack release streams

The image stream tracks the OpenStack release cycle (e.g. 2026.1 Gazpacho) and corresponds to the openstack-ceph-config-helper-<stream> apk. Tags are the stream (2026.1) and latest; the bundled Ceph release is not a tag, since it moves with Ceph updates.

Getting Started

Point the chart's ceph-config-helper image slots at this image. Each chart has several of them; set every one, for example:

• ceph-adapter-rook: images.tags.ceph_config_helper
• cinder: images.tags.cinder_storage_init and images.tags.cinder_backup_storage_init
• glance: images.tags.glance_storage_init
• libvirt: images.tags.ceph_config_helper
• nova: images.tags.nova_storage_init, images.tags.nova_wait_for_computes_init and images.tags.nova_service_cleaner

The charts supply the command, and set the user for each job. For example, for glance:

images:
  tags:
    glance_storage_init: cgr.dev/ORGANIZATION/openstack-ceph-config-helper:2026.1

These are the charts this image is tested with. Other openstack-helm charts default to ceph-config-helper too (ceph-client, ceph-rgw, ceph-mon, ceph-osd, ceph-provisioners, ovn, gnocchi, elasticsearch, cert-rotation) but are not validated; jobs in them that set no user, such as ceph-client's cronjobs, run as nonroot here.

Documentation and Resources

• openstack-helm documentation
• ceph-config-helper image source
• Ceph documentation

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.