NetBox
NetBox 4.7's patch run fixes a token leak and a broken restore path.
Comparison · Infra & APIs
Coder vs runc
A side-by-side editorial comparison of Coder and runc — release velocity, themes, recent moves, and the top alternatives to consider.
Coder vs runc: at a glance
What is Coder?
Coder now patches three release lines at once, and the fixes keep landing on agent access.
Coder's feed shows patch releases on v2.29, v2.34 and v2.36 within three days, which means a v2.35 and a v2.36 mainline shipped that this feed never captured. The late-October fixes are permission work: new API keys stay within the caller's scopes, fetching external agent credentials now requires SSH permission, and read_skill_file reads are confined to the skill directory. Everything else is release-script and DERP client fixes.
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.
Coder vs runc: editorial side-by-side
Coder
5.0INFRA · APIS
Coder now patches three release lines at once, and the fixes keep landing on agent access.
◆ Current state
Coder's feed shows patch releases on v2.29, v2.34 and v2.36 within three days, which means a v2.35 and a v2.36 mainline shipped that this feed never captured. The late-October fixes are permission work: new API keys stay within the caller's scopes, fetching external agent credentials now requires SSH permission, and read_skill_file reads are confined to the skill directory. Everything else is release-script and DERP client fixes.
◆ Where it's heading
The security surface is moving to the AI agent features. Two of the three substantive fixes this round concern what an agent can read or which credentials it can obtain, following the June hardening drop on OIDC linking and token theft. The multi-branch backporting continues, so enterprise customers on older lines like 2.29 still get the same permission fixes as the mainline.
◆ Prediction
Expect more permission checks around agent credentials and skills as those features get exercised; the feature releases themselves are not visible in this feed, so their direction is unclear 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 Coder 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 Coder or runc.
Apptainer
Apptainer's CDI support needed a privilege-escalation fix four months after it shipped.
Cobbler
Cobbler's 3.3 branch adds Kerberos single sign-on to the web UI.
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.
Recent activity from Coder and runc
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoCoderv2.34.17 confines skill file reads to the skill directory
- 2d agoCoderv2.36.12 confines skill file reads to the skill directory
- 4d agoCoderv2.29.24 backports API key scope and agent credential checks
- 4d agoCoderv2.34.16 backports API key scope and agent credential checks
- 4d agoCoderv2.36.11 scopes new API keys and gates agent credentials
- 26d agoruncRelease candidate lifts 1024-CPU limit, removes deprecated APIs
- 1mo agoruncWorkaround for kernel bug that crashed runc on cgroup v2
- 1mo agoCoderv2.34.10
- 3mo agorunctmpfs regression on Ubuntu 20.04 kernels fixed
- 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
Frequently asked questions
What is the difference between Coder and runc?
They serve adjacent needs but don't currently overlap on shipped themes. Coder 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 Coder better than runc?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Coder 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 Coder?
Top Coder alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Coder alternatives" section above for the current picks, or visit /alternatives/coder 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.