Prometheus Alertmanager
Alertmanager 0.34.2 turns off CORS by default, breaking cross-origin API calls.
Comparison · Infra & APIs
NetBox vs runc
A side-by-side editorial comparison of NetBox and runc — release velocity, themes, recent moves, and the top alternatives to consider.
NetBox vs runc: at a glance
What is NetBox?
NetBox 4.7's patch run fixes a token leak and a broken restore path.
Four 4.7 patches followed the September 4.7.0 release. 4.7.1 reinstalled hierarchical-path triggers that a pg_dump restore silently dropped, 4.7.2 stopped background bulk requests recording plaintext API tokens in job results, 4.7.3 was a REST and GraphQL performance release, and 4.7.4 adds change-log IDs to webhook payloads, fixes the circuit status GraphQL enum and warns about a thumbnail storage change.
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.
NetBox vs runc: editorial side-by-side
NetBox
5.0INFRA · APIS
NetBox 4.7's patch run fixes a token leak and a broken restore path.
◆ Current state
Four 4.7 patches followed the September 4.7.0 release. 4.7.1 reinstalled hierarchical-path triggers that a pg_dump restore silently dropped, 4.7.2 stopped background bulk requests recording plaintext API tokens in job results, 4.7.3 was a REST and GraphQL performance release, and 4.7.4 adds change-log IDs to webhook payloads, fixes the circuit status GraphQL enum and warns about a thumbnail storage change.
◆ Where it's heading
The ltree migration in 4.7.0 is still generating follow-up work, and the patch notes are candid about what broke. Performance work on REST serialisation and GraphQL has been steady across the line, and event payloads are getting richer for automation users.
◆ Prediction
Expect further 4.7.x patches on a two-week rhythm with more API performance fixes; the entries don't show what 4.8 will contain.
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 NetBox 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 NetBox or runc.
nfs-ganesha
NFS-Ganesha's 15.x line turns to weekly fixes, input checks and dropping 9P.
Kata Containers
Kata Containers 4.3 fixes a guest-to-host escape and tightens annotation handling.
mod_auth_openidc
mod_auth_openidc 2.4.20.4 closes a provider-to-host command execution path.
Scrypted
Scrypted's v0.147.0 pairs RTSP compliance fixes with two web-server security patches.
Daytona
Daytona adds warm pools and spot GPU support, targeting production-grade AI agent sandbox execution.
Recent activity from NetBox and runc
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 5d agoNetBox4.7.4 adds change-log IDs to webhooks, renames a GraphQL enum
- 19d agoNetBox4.7.3 speeds up REST serialisation and fixes cable paths
- 26d agoruncRelease candidate lifts 1024-CPU limit, removes deprecated APIs
- 1mo agoNetBox4.7.2 stops API tokens leaking into job results
- 1mo agoruncWorkaround for kernel bug that crashed runc on cgroup v2
- 1mo agoNetBox4.7.1 restores hierarchy triggers lost on database restore
- 2mo agoNetBoxNetBox v4.7.0 ⚡
- 2mo agoNetBoxNetBox v4.6.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 NetBox and runc?
They serve adjacent needs but don't currently overlap on shipped themes. NetBox 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 NetBox better than runc?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. NetBox 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 NetBox?
Top NetBox alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "NetBox alternatives" section above for the current picks, or visit /alternatives/netbox 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.