Oh Dear
Oh Dear's weekly changelogs have carried a security section five weeks running.
Comparison · Infra & APIs
AdGuard Home vs runc
A side-by-side editorial comparison of AdGuard Home and runc — release velocity, themes, recent moves, and the top alternatives to consider.
AdGuard Home vs runc: at a glance
What is AdGuard Home?
AdGuard Home renames its next release: the 0.108 beta line becomes v1.0.0.
The beta channel has moved to the new UI and versioning scheme, and the first build under it is v1.0.0-b.1, published two days after v0.108.0-b.91. It carries a Go security update, a fix for reading partially received TCP prefixes and a command-line update panic fix, and drops macOS 13 support as a consequence of Go 1.27. The stable line last moved with 0.107.79 in August.
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.
AdGuard Home vs runc: editorial side-by-side
AdGuard Home
0.0INFRA · APIS
AdGuard Home renames its next release: the 0.108 beta line becomes v1.0.0.
◆ Current state
The beta channel has moved to the new UI and versioning scheme, and the first build under it is v1.0.0-b.1, published two days after v0.108.0-b.91. It carries a Go security update, a fix for reading partially received TCP prefixes and a command-line update panic fix, and drops macOS 13 support as a consequence of Go 1.27. The stable line last moved with 0.107.79 in August.
◆ Where it's heading
What began on the edge channel in August has reached beta, and the version number now states the ambition: the long-running 0.x project is preparing a 1.0. Fix lists on the beta remain short and focused on correctness and Go updates, which suggests the work is converging rather than adding scope.
◆ Prediction
More v1.0.0 betas are likely before a stable 1.0, and the new UI will arrive for stable users with it. No date or candidate is given in these notes.
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 AdGuard Home 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 AdGuard Home 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.
All Quiet
All Quiet moves from enterprise integrations to the on-call engineer's own day.
Robusta
Robusta's recent releases patch its runner image rather than add features.
See all AdGuard Home alternatives → · See all runc alternatives →
Recent activity from AdGuard Home and runc
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 26d agoruncRelease candidate lifts 1024-CPU limit, removes deprecated APIs
- 1mo agoAdGuard HomeBeta channel moves to the new UI as v1.0.0-b.1
- 1mo agoAdGuard HomeBeta b.91 fixes DHCP lease persistence and DNS64 chains
- 1mo agoruncWorkaround for kernel bug that crashed runc on cgroup v2
- 2mo agoAdGuard HomeAdGuard Home 0.107.79 hardens DNS-over-QUIC against exhaustion
- 3mo agoAdGuard HomeBeta b.90 carries the DNS-over-QUIC exhaustion fix
- 3mo agoAdGuard HomeBeta b.89 hardens against JIGGLE attacks (GHSA-p5f5-3p5g-rfjw)
- 3mo agorunctmpfs regression on Ubuntu 20.04 kernels fixed
- 3mo agoAdGuard Home0.107.78: over half the changelog is security fixes
- 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 AdGuard Home 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 AdGuard Home 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 AdGuard Home?
Top AdGuard Home alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "AdGuard Home alternatives" section above for the current picks, or visit /alternatives/adguard-home 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.