Oh Dear
Oh Dear's weekly changelogs have carried a security section five weeks running.
Comparison · Infra & APIs
All Quiet vs runc
A side-by-side editorial comparison of All Quiet and runc — release velocity, themes, recent moves, and the top alternatives to consider.
All Quiet vs runc: at a glance
What is All Quiet?
All Quiet moves from enterprise integrations to the on-call engineer's own day.
All Quiet is an incident management and on-call tool. Three releases on 28 September rebuilt the on-call calendar with effective and detailed views and overrides from any cell, added recurring snooze windows per integration plus detection of incidents that resolve themselves quickly, and introduced a personal on-call dashboard with shift summaries and noise metrics. Before that, August and early September added scoped API keys, Salesforce and Jira two-way sync and webhook rate-limit alerts.
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.
All Quiet vs runc: editorial side-by-side
All Quiet
0.0INFRA · APIS
All Quiet moves from enterprise integrations to the on-call engineer's own day.
◆ Current state
All Quiet is an incident management and on-call tool. Three releases on 28 September rebuilt the on-call calendar with effective and detailed views and overrides from any cell, added recurring snooze windows per integration plus detection of incidents that resolve themselves quickly, and introduced a personal on-call dashboard with shift summaries and noise metrics. Before that, August and early September added scoped API keys, Salesforce and Jira two-way sync and webhook rate-limit alerts.
◆ Where it's heading
The summer work targeted buyers: access control and integrations that larger organisations require. The September work targets responders: less noise, clearer schedules and a view of one's own shifts. Noise detection for auto-resolving incidents is the most consequential piece, since it turns alert fatigue into a metric teams can act on.
◆ Prediction
Expect noise metrics to feed into suppression or routing rules, since detection without action is the obvious next gap. The feed has no entries after 28 September.
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 All Quiet 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 All Quiet or runc.
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.
KubeArmor
KubeArmor ships fixes as release-candidate tags, and its feed misses the finals.
Robusta
Robusta's recent releases patch its runner image rather than add features.
Uptrends
Uptrends spent October on account plumbing: vault credentials, bulk edits and a free trial path.
See all All Quiet alternatives → · See all runc alternatives →
Recent activity from All Quiet and runc
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 26d agoruncRelease candidate lifts 1024-CPU limit, removes deprecated APIs
- 1mo agoAll QuietIntegration Snooze Windows and Auto-Resolved Noise Detection
- 1mo agoAll QuietPersonal On-Call Dashboard and Team Activity Metrics
- 1mo agoAll QuietOn-Call Calendars: Interactive Overrides, Timeline Views, and Schedule Controls
- 1mo agoruncWorkaround for kernel bug that crashed runc on cgroup v2
- 2mo agoAll QuietWebhook Rate Limit Alerts and Diagnostics
- 2mo agoAll QuietJira Integration: Precise Field Mapping and Safer Two-Way Sync
- 2mo agoAll QuietPublish and Unpublish Comments
- 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 All Quiet 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 All Quiet 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 All Quiet?
Top All Quiet alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "All Quiet alternatives" section above for the current picks, or visit /alternatives/allquiet 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.