Pro node images

Warewulf Pro ships pre-built node images that, combined with the Pro overlays, give you a turn-key compute node for common HPC scheduler stacks. The images are tested by CIQ for specific scheduler-and-OS combinations.

For general node image concepts - importing, building, customizing - see the upstream node images documentation.

Catalog

rockylinux-ohpc

Rocky Linux 9 base image with OpenHPC 3 packages installed. Serves as the foundation for the scheduler-specific images, and can also be deployed independently for sites that build their own scheduler client on top.

Available tags: 3

rockylinux-slurm

Compute node image for a Slurm cluster. Built on rockylinux-ohpc with the OpenHPC Slurm client added.

Available tags: 24 (Slurm 24), 25 (Slurm 25 - newer versions ship with newer base OS).

rockylinux-openpbs

Compute node image for an OpenPBS cluster. Built on rockylinux-ohpc with the OpenPBS execution client added.

Available tags: 22 (OpenPBS 22).

rlc-fuzzball-substrate

Rocky Linux from CIQ image with Fuzzball Substrate packages installed. Used for joining compute nodes to a Fuzzball Orchestrate cluster. This image is only available in the RLC variant — there is no community-Rocky build.

Requires: an RLC entitlement in addition to Warewulf Pro. See RLC variants below.

Importing images

The Pro images are distributed as OCI artifacts in CIQ Depot at docker://depot.ciq.com/warewulf-pro/warewulf-node-images/. Import directly with wwctl:

# export WAREWULF_OCI_USERNAME=user@example.com
# export WAREWULF_OCI_PASSWORD=<depot access key>
# export IMAGES=docker://depot.ciq.com/warewulf-pro/warewulf-node-images
# wwctl image import $IMAGES/rockylinux-ohpc:3 ohpc-3
# wwctl image import $IMAGES/rockylinux-slurm:24 slurm-24
# wwctl image import $IMAGES/rockylinux-openpbs:22 openpbs-22

Generate a Depot access key from CIQ Portal under My Account → Access Keys.

Multi-architecture support

Starting with Warewulf Pro v1.2.0, every Pro node image is published for both x86_64 and aarch64. Import them with the same wwctl image import commands shown under Importing images above.

Each image is published as a single multi-architecture manifest under one tag, so on a Warewulf server that matches the node architecture the standard wwctl image import above pulls the right build automatically.

For a mixed-architecture cluster, use wwctl image import --platform to select a specific architecture (amd64 or arm64), import each under its own local name, then point per-architecture profiles at the matching image:

# wwctl image import --platform amd64 $IMAGES/rockylinux-slurm:24 slurm-24-x86_64
# wwctl image import --platform arm64 $IMAGES/rockylinux-slurm:24 slurm-24-arm64
# wwctl profile add x86-compute   --image slurm-24-x86_64
# wwctl profile add arm64-compute --image slurm-24-arm64

Warewulf v4.6.5 (shipped in Pro v1.2.0) also adds cross-architecture support for wwclient, via the wwclient.aarch64 and wwclient.x86_64 overlays.

RLC variants

Customers who hold both a Warewulf Pro entitlement and a Rocky Linux from CIQ (RLC) entitlement gain access to RLC-based variants of every Pro node image. The RLC images have the same scheduler integrations and are built, configured, and used identically to the community-Rocky-based images — the base OS is RLC instead of community Rocky Linux.

Available RLC images

Accessing RLC images

RLC variants are distributed in a separate Depot repository - warewulf-pro-rlc - which is activated automatically for customers with both entitlements.

# depot enable warewulf-pro-rlc
# wwctl image import docker://depot.ciq.com/warewulf-pro-rlc/warewulf-pro-rlc/rlc-slurm:24 slurm-24

Why use RLC images

• Quality and performance modifications that CIQ applies on top of Rocky Linux.
• Coordinated support - a single support contact for both the OS and the cluster provisioning layer.
• Long-term support - RLC's LTS lifecycle applies to the cluster node OS.

For RLC details, see the Rocky Linux from CIQ documentation.

Customizing a Pro image

Pro images are standard OCI images - you can extend them with wwctl image shell or by building a derivative Containerfile. For the customization workflow, see the upstream image creation guide.