Sarus Suite: Cloud-native Containers for HPC

TL;DR

Sarus Suite is a cloud-native HPC container architecture built on Podman that maintains upstream compatibility while adding HPC-specific features, enabling scalable, high-performance, and flexible container workflows.

Contribution

It introduces Sarus Suite, an HPC container solution aligned with upstream container ecosystems, integrating HPC functionalities through system layers without requiring a specialized runtime.

Findings

Sarus Suite matches the performance and scaling of existing HPC container baselines.

It enables faster per-node container startup compared to traditional HPC container solutions.

Supports direct use of upstream OCI images and Kubernetes-based multi-container workflows.

Abstract

High-performance computing (HPC) systems must support fast-moving software stacks, especially in AI/ML, while preserving scheduler control, scalable startup, and production performance. Yet many HPC container solutions rely on specialized runtime stacks that weaken continuity with mainstream cloud-native workflows and require ongoing effort to sustain compatibility with the evolving upstream ecosystem. We argue that HPC should specialize the integration layer while keeping the container engine aligned with upstream container evolution. We present Sarus Suite, an upstream-aligned HPC container architecture built around an unchanged Podman engine. Sarus Suite adds the HPC-specific functionality needed for production use through complementary system layers for declarative runtime specification, scheduler-native execution, scalable shared-image access, and standards-based host capability injection. We evaluate Sarus Suite on a Cray EX GH200 system using communication-intensive HPC workloads, large scale AI training, metadata-heavy startup workloads, and container startup measurements. Across PyFR, SPH-EXA, Megatron-LM, and Pynamic, Sarus Suite matches the performance and scaling of the production Enroot+Pyxis baseline while delivering consistently faster per-node container startup. The architecture also enables direct use of upstream OCI images, including NGC-based images, and supports cloud-native multi-container workflows expressed through Kubernetes manifests. These results show that HPC-grade containers do not require an HPC-specific runtime, provided that scheduler semantics, scalable image access, and host integration are implemented in explicit system layers. This preserves upstream continuity and software agility while maintaining scheduler control, scalability, and production performance.