NetBox
NetBox 4.7's patch run fixes a token leak and a broken restore path.
Comparison · Infra & APIs
Apptainer vs runc
A side-by-side editorial comparison of Apptainer and runc — release velocity, themes, recent moves, and the top alternatives to consider.
Apptainer vs runc: at a glance
What is Apptainer?
Apptainer's CDI support needed a privilege-escalation fix four months after it shipped.
Apptainer 1.5.0 in May added Container Device Interface support, a BuildKit bootstrap for building SIF images from Dockerfiles, and IPFS pulls. The point releases since have handled the cost. 1.5.4 fixed a high-severity local privilege escalation in suid mode by stopping non-root users from passing --cdi-dirs, added a config default for CDI directories, and restored rootless builds on Ubuntu 24.04 and later. 1.5.5 raises the minimum Go version to block compromised emSign intermediate certificates and fixes pull destinations and suid fakeroot mounts.
What is runc?
runc 1.6.0-rc.1 lifts the 1024-CPU limit and refuses settings it used to quietly ignore
The 1.6.0 cycle opened on October 6 with a first release candidate that is mostly cleanup: deprecated libcontainer APIs removed, Go 1.26 now required, urfave/cli moved from v1 to v3, and the binary about 15% smaller on amd64. The changes with operational weight are that cpuAffinity and NUMA memoryPolicy no longer stop at 1024 CPUs or nodes, and that a container asking for a read-only rootfs without its own mount namespace is now refused. Eleven days earlier 1.5.2 worked around a kernel bug, present since v6.17, that corrupted memory inside runc and caused random crashes on cgroup v2. It also stopped runc exec --cgroup from escaping into a sibling cgroup.
Apptainer vs runc: editorial side-by-side
Apptainer
2.5INFRA · APIS
Apptainer's CDI support needed a privilege-escalation fix four months after it shipped.
◆ Current state
Apptainer 1.5.0 in May added Container Device Interface support, a BuildKit bootstrap for building SIF images from Dockerfiles, and IPFS pulls. The point releases since have handled the cost. 1.5.4 fixed a high-severity local privilege escalation in suid mode by stopping non-root users from passing --cdi-dirs, added a config default for CDI directories, and restored rootless builds on Ubuntu 24.04 and later. 1.5.5 raises the minimum Go version to block compromised emSign intermediate certificates and fixes pull destinations and suid fakeroot mounts.
◆ Where it's heading
The 1.5 line is spending its point releases on the edges of the features it added: CDI's flexibility turned into an escalation path under suid, and unprivileged builds keep breaking as distributions tighten AppArmor and drop tools. The fix for CDI was to move control to the admin's config file, a pattern suid deployments will likely see more of.
◆ Prediction
Expect more 1.5.x releases on unprivileged build compatibility and suid restrictions; further CDI coverage remains the most likely feature addition.
runc
2.5INFRA · APIS
runc 1.6.0-rc.1 lifts the 1024-CPU limit and refuses settings it used to quietly ignore
◆ Current state
The 1.6.0 cycle opened on October 6 with a first release candidate that is mostly cleanup: deprecated libcontainer APIs removed, Go 1.26 now required, urfave/cli moved from v1 to v3, and the binary about 15% smaller on amd64. The changes with operational weight are that cpuAffinity and NUMA memoryPolicy no longer stop at 1024 CPUs or nodes, and that a container asking for a read-only rootfs without its own mount namespace is now refused. Eleven days earlier 1.5.2 worked around a kernel bug, present since v6.17, that corrupted memory inside runc and caused random crashes on cgroup v2. It also stopped runc exec --cgroup from escaping into a sibling cgroup.
◆ Where it's heading
The project keeps converting silent behaviour into explicit behaviour. Read-only requests that were ignored now fail, a umask that was dropped is now honoured, and poststart hooks moved to conform to the runtime spec. The same maintainers are shrinking the surface underneath, dropping the deprecated API and the high-level cilium/ebpf path, which took roughly 7.5% off the 1.5.2 binary. Stricter behaviour plus a smaller dependency set is what a component under every container host would be expected to do between majors.
◆ Prediction
1.5.0's notes pointed to a 1.6.0 in late October 2026, and the feed so far shows only rc.1, so further release candidates or the final are the next entries to expect. The refused read-only configurations are the change most likely to surface as user reports during testing.
Alternatives to Apptainer and runc
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 runc.
Cobbler
Cobbler's 3.3 branch adds Kerberos single sign-on to the web UI.
Coder
Coder now patches three release lines at once, and the fixes keep landing on agent access.
Oh Dear
Oh Dear's weekly changelogs have carried a security section five weeks running.
Apache ShenYu
ShenYu's AI gateway plugins are back in motion, with 2.7.2 candidate tags in October.
TestingBot
TestingBot's autumn work is plumbing: a rebuilt tunnel and another bug-tracker link.
See all Apptainer alternatives → · See all runc alternatives →
Recent activity from Apptainer and runc
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 10d agoApptainer1.5.5 blocks compromised emSign CA certs via Go update
- 26d agoruncRelease candidate lifts 1024-CPU limit, removes deprecated APIs
- 1mo agoruncWorkaround for kernel bug that crashed runc on cgroup v2
- 1mo agoApptainer1.5.4 fixes suid privilege escalation via --cdi-dirs
- 3mo agoApptainer1.5.3 works around missing ptrace and getopt on newer distros
- 3mo agorunctmpfs regression on Ubuntu 20.04 kernels fixed
- 4mo agoApptainer1.5.2 extends the mksquashfs workaround and improves FIPS errors
- 4mo agoruncrunc 1.5.0 stable, with dated support windows for older branches
- 4mo agoruncCVE-2026-41579: /dev symlink host write access fixed
- 4mo agoruncRelease candidate carrying the CVE-2026-41579 fix
- 5mo agoApptainer1.5.1 fixes a prefix-matching flaw in limit container paths
- 5mo agoApptainerApptainer 1.5 adopts CDI and adds a BuildKit image bootstrap ⚡
Frequently asked questions
What is the difference between Apptainer and runc?
They serve adjacent needs but don't currently overlap on shipped themes. Apptainer and runc are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Apptainer better than runc?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Apptainer and runc are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). 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 runc?
Top runc alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "runc alternatives" section above for the current picks, or visit /alternatives/runc for the full list with editorial commentary on each.