← Back to home
Comparison · Infra & APIs

Apptainer vs Skipper

A side-by-side editorial comparison of Apptainer and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.

Apptainer vs Skipper: at a glance

FeatureApptainerSkipper
SectorInfra & APIsInfra & APIs
Velocity score2.55.0
Sparks · 30d00
Top themescontainers, hpc, cdi, acceleratorsreverse-proxy, kubernetes, memory-footprint, zone-aware-routing
Last editorial update10d ago1h ago
WebsiteVisit →Visit →

What is Apptainer?

Apptainer 1.5 adds CDI device support and builds SIF images straight from Dockerfiles.

Apptainer shipped 1.5.0 in May after two release candidates, and has issued three point releases since. The major adds a subset of the Container Device Interface standard through --device and --cdi-dirs, selective mounting for Intel Gaudi accelerators, a buildkit: bootstrap that builds SIF images from a Dockerfile without Docker or Podman, and image pulls from an IPFS gateway. The point releases since have been almost entirely about the unprivileged build path — PRoot, mksquashfs and fuse2fs — plus a path-matching CVE in the suid limit container paths directive.

Read the full Apptainer trajectory →

What is Skipper?

Skipper trims a 4x memory regression out of routesrv, days after shipping h2c

Zalando's HTTP router ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.63, which stops routesrv holding an uncompressed route tree alongside the compressed buffer: retained memory in the release's own benchmark falls from 30.7 MB to 2.0 MB, undoing most of the 4x increase zone-aware routing had introduced. Around it sit narrow auth repairs, and an eskip parser change that finally accepts negative numeric arguments in predicates and filters.

Read the full Skipper trajectory →

Apptainer vs Skipper: editorial side-by-side

A
Apptainer
INFRA · APIS
2.5

Apptainer 1.5 adds CDI device support and builds SIF images straight from Dockerfiles.

◆ Current state

Apptainer shipped 1.5.0 in May after two release candidates, and has issued three point releases since. The major adds a subset of the Container Device Interface standard through --device and --cdi-dirs, selective mounting for Intel Gaudi accelerators, a buildkit: bootstrap that builds SIF images from a Dockerfile without Docker or Podman, and image pulls from an IPFS gateway. The point releases since have been almost entirely about the unprivileged build path — PRoot, mksquashfs and fuse2fs — plus a path-matching CVE in the suid limit container paths directive.

◆ Where it's heading

The 1.5 line is Apptainer catching up to how accelerators are actually exposed in 2026: CDI is the standard NVIDIA, Intel and others have converged on, and adopting it replaces per-vendor mount logic with a declarative spec the container runtime reads. The Gaudi support is the first vendor-specific case built on that footing. Separately, the buildkit bootstrap attacks the other friction point — needing a Docker daemon to build an image for a cluster that deliberately does not run one. The point-release churn shows where the cost lands: the bundled PRoot and squashfs tooling that makes unprivileged builds work is fragile across distributions, and 1.5.1 quietly documents that PRoot is no longer built on ppc, s390 or riscv at all.

◆ Prediction

Expect further CDI coverage as the obvious next step, since only a subset of the standard is implemented and each accelerator vendor currently needs its own flag. The unprivileged build path is the likely source of the next point release, given that three of the last three have been spent there.

S
Skipper
INFRA · APIS
5.0

Skipper trims a 4x memory regression out of routesrv, days after shipping h2c

◆ Current state

Zalando's HTTP router ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.63, which stops routesrv holding an uncompressed route tree alongside the compressed buffer: retained memory in the release's own benchmark falls from 30.7 MB to 2.0 MB, undoing most of the 4x increase zone-aware routing had introduced. Around it sit narrow auth repairs, and an eskip parser change that finally accepts negative numeric arguments in predicates and filters.

◆ Where it's heading

Two threads run through the recent tags. The data path keeps getting real work - leastRequests balancing, then h2c end to end in v0.27.57, now the memory cost of zone-aware routing being paid back. The auth filters, by contrast, are only being maintained: token introspection, grant auth, and now the OIDC Referer handling are fixes rather than new capability, and several are follow-ups to each other rather than independent bugs.

◆ Prediction

Zone-aware routing looks like the source of the recent memory attention, so expect further tuning around route storage and the hash computation done on every pull, which the release's second benchmark already isolates. The OIDC cookie change is the second link in an auth chain that started with the grant-auth fix, and is likely to draw another follow-up.

Alternatives to Apptainer and Skipper

Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Apptainer or Skipper.

See all Apptainer alternatives → · See all Skipper alternatives →

Recent activity from Apptainer and Skipper

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 15h agoSkipperMove OIDC flow protection from Referer to cookies
  2. 15h agoSkipperv0.27.63: Store routes compressed-only, decompress on demand (#4198)
  3. 1d agoSkipperEskip predicates and filters accept negative numbers
  4. 1d agoSkipperFix token introspection handling
  5. 1d agoSkipperFix grant auth flow
  6. 1d agoSkipperUpdate outdated golang.org/x dependencies
  7. 29d agoApptainer1.5.3 works around missing ptrace and getopt on newer distros
  8. 1mo agoApptainer1.5.2 extends the mksquashfs workaround and improves FIPS errors
  9. 2mo agoApptainer1.5.1 fixes a prefix-matching flaw in limit container paths
  10. 3mo agoApptainerApptainer 1.5 adopts CDI and adds a BuildKit image bootstrap
  11. 4mo agoApptainerSecond 1.5.0 candidate adds loong64 and a BuildKit host override
  12. 5mo agoApptainerFirst 1.5.0 candidate previews CDI, BuildKit and IPFS support

Frequently asked questions

What is the difference between Apptainer and Skipper?

They serve adjacent needs but don't currently overlap on shipped themes. Skipper is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Apptainer better than Skipper?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Skipper is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to Apptainer?

Top Apptainer alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Apptainer alternatives" section above for the current picks, or visit /alternatives/apptainer for the full list with editorial commentary on each.

What are the best alternatives to Skipper?

Top Skipper alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Skipper alternatives" section above for the current picks, or visit /alternatives/skipper for the full list with editorial commentary on each.