NetBox
NetBox 4.7's patch run fixes a token leak and a broken restore path.
Comparison · Infra & APIs
Cobbler vs runc
A side-by-side editorial comparison of Cobbler and runc — release velocity, themes, recent moves, and the top alternatives to consider.
Cobbler vs runc: at a glance
What is Cobbler?
Cobbler's 3.3 branch adds Kerberos single sign-on to the web UI.
Cobbler's public releases are all 3.3-branch backports. 3.3.10 adds Kerberos/GSSAPI single sign-on for the web UI through an Apache-terminated bridge and hardens the passthru authentication module against timing attacks. It follows the 3.3.8/3.3.9 pair, which brought openSUSE Leap 16 and Agama installer support, XCP-ng network installs and Python 3.13 support, and had to be re-cut after a CI publishing failure.
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.
Cobbler vs runc: editorial side-by-side
Cobbler
0.0INFRA · APIS
Cobbler's 3.3 branch adds Kerberos single sign-on to the web UI.
◆ Current state
Cobbler's public releases are all 3.3-branch backports. 3.3.10 adds Kerberos/GSSAPI single sign-on for the web UI through an Apache-terminated bridge and hardens the passthru authentication module against timing attacks. It follows the 3.3.8/3.3.9 pair, which brought openSUSE Leap 16 and Agama installer support, XCP-ng network installs and Python 3.13 support, and had to be re-cut after a CI publishing failure.
◆ Where it's heading
The branch is still gaining features aimed at enterprise data centres rather than winding down: new installer ecosystems in August, directory-backed single sign-on now. Authentication has been a recurring concern since the CVE-2024-47533 admin-API bypass. Releases continue to arrive as rollups from main.
◆ Prediction
Expect further 3.3.x rollups; whether the main line cuts a 3.4 is not visible from these entries.
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 Cobbler 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 Cobbler or runc.
Apptainer
Apptainer's CDI support needed a privilege-escalation fix four months after it shipped.
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 Cobbler alternatives → · See all runc alternatives →
Recent activity from Cobbler and runc
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 26d agoruncRelease candidate lifts 1024-CPU limit, removes deprecated APIs
- 1mo agoruncWorkaround for kernel bug that crashed runc on cgroup v2
- 1mo agoCobbler3.3.10 adds Kerberos single sign-on to the web UI
- 2mo agoCobbler3.3.8 re-cut after fixing the PyPI publish workflow
- 2mo agoCobblerLeap 16 and Agama support, withdrawn as defunct
- 3mo agorunctmpfs regression on Ubuntu 20.04 kernels fixed
- 3mo agoCobblerCVE-2024-47533 backported to the 3.2 branch
- 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
- 1y agoCobblerCVE-2024-47533: API admin authentication bypass fixed
- 2y agoCobblerEFI support added to cobbler buildiso
Frequently asked questions
What is the difference between Cobbler and runc?
They serve adjacent needs but don't currently overlap on shipped themes. runc is currently shipping more aggressively (velocity 2.5 vs 0.0), 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 Cobbler better than runc?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. runc is currently shipping more aggressively (velocity 2.5 vs 0.0), 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 Cobbler?
Top Cobbler alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Cobbler alternatives" section above for the current picks, or visit /alternatives/cobbler 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.