openstack-ironic-oshelm

packaged by Chainguard

Chainguard Container for openstack-ironic-oshelm

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

• The image runs as the ironic account (uid/gid 42424, home /var/lib/ironic) by default, where the upstream image runs as root. The chart runs the ironic-api Deployment and the db-sync job as the image user and the conductor StatefulSet as root, so chart deployments are unaffected.
• One image serves every ironic workload the chart deploys: the ironic-api Deployment (the Bare Metal API under uwsgi), the ironic-conductor StatefulSet with its pxe (TFTP) container and init containers, the optional ironic-novncproxy Deployment, and the db-sync job.
• 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, ironic-*, and python.
• The conductor pod's tools are included: bash, iproute2, ethtool, lshw, qemu-img, ipmitool for the ipmi hardware type, and in.tftpd (tftp-hpa) at /usr/sbin/in.tftpd. The redfish hardware type's sushy library is in the virtualenv.
• iPXE boot files are included at /usr/lib/ipxe, where the conductor's pxe-init container copies them from: undionly.kpxe, ipxe.efi and snponly.efi for x86_64 nodes on amd64, and arm64 builds of ipxe.efi and snponly.efi on arm64. To boot x86_64 nodes from an arm64 conductor, or to use PXELINUX (pxelinux.0, not included), point the chart's ironic_pxe_init image at a derived image with those files in /usr/lib/ipxe.
• The noVNC web assets are not included, as in the upstream image, so the optional ironic-novncproxy Deployment needs them mounted at /usr/share/novnc (its [vnc]novnc_web default) to start.
• socat and shellinabox are not included, so the ipmitool-socat and ipmitool-shellinabox serial console interfaces are unavailable.
• The ilo, irmc, and snmp hardware types are not available: their client libraries are not in the virtualenv.

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

Getting Started

Point every ironic image slot of the chart at this image:

images:
  tags:
    ironic_api: cgr.dev/ORGANIZATION/openstack-ironic-oshelm:latest
    ironic_conductor: cgr.dev/ORGANIZATION/openstack-ironic-oshelm:latest
    ironic_db_sync: cgr.dev/ORGANIZATION/openstack-ironic-oshelm:latest
    ironic_novncproxy: cgr.dev/ORGANIZATION/openstack-ironic-oshelm:latest
    ironic_pxe: cgr.dev/ORGANIZATION/openstack-ironic-oshelm:latest
    ironic_pxe_init: cgr.dev/ORGANIZATION/openstack-ironic-oshelm:latest

Then install the chart from the openstack-helm repository:

helm repo add openstack-helm https://tarballs.opendev.org/openstack/openstack-helm
helm upgrade --install ironic openstack-helm/ironic --namespace openstack --values values.yaml

The chart's other image slots (the database, keystone, RabbitMQ, bootstrap, and cleaning-network jobs, and the nginx HTTP boot server) use the openstack-client, rabbitmq, and nginx images and are unaffected.

Configuration

Configuration comes from the chart, which renders ironic.conf and the uwsgi configuration under /etc/ironic/ and the TFTP map file at /tftp-map-file. By default the chart enables the ipmi and redfish hardware types and expects Neutron for the cleaning and provisioning networks, Glance for deploy images, and a provisioning interface named ironic-pxe on the conductor's host. See the openstack-helm ironic chart and the upstream ironic configuration reference for the full set of options.

Documentation and Resources

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