Oh Dear
Oh Dear's weekly changelogs have carried a security section five weeks running.
Comparison · Infra & APIs
Inspektor Gadget vs runc
A side-by-side editorial comparison of Inspektor Gadget and runc — release velocity, themes, recent moves, and the top alternatives to consider.
Inspektor Gadget vs runc: at a glance
What is Inspektor Gadget?
Inspektor Gadget keeps cutting the privileges an eBPF tool has to ask for.
Inspektor Gadget v0.57.0 lets gadgets run rootless with cap_bpf, cap_perfmon and cap_sys_ptrace, and adds a flag that drops CAP_SYS_ADMIN on Kubernetes deployments. v0.56.0 introduced experimental multi-tenancy through TokenReview and RBAC. The v0.56.1 and v0.56.2 patches backported USDT parsing fixes, so crafted binaries cannot crash the process or exhaust memory, and bounded owner reference enrichment.
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.
Inspektor Gadget vs runc: editorial side-by-side
Inspektor Gadget
2.5INFRA · APIS
Inspektor Gadget keeps cutting the privileges an eBPF tool has to ask for.
◆ Current state
Inspektor Gadget v0.57.0 lets gadgets run rootless with cap_bpf, cap_perfmon and cap_sys_ptrace, and adds a flag that drops CAP_SYS_ADMIN on Kubernetes deployments. v0.56.0 introduced experimental multi-tenancy through TokenReview and RBAC. The v0.56.1 and v0.56.2 patches backported USDT parsing fixes, so crafted binaries cannot crash the process or exhaust memory, and bounded owner reference enrichment.
◆ Where it's heading
The direction is lower trust: fewer privileges for the tool and less trust in the binaries it inspects. Multi-tenancy, rootless runs and hardened ELF parsing all remove reasons a security team would refuse to deploy it. GPU telemetry from v0.55 has no follow-up in the recent notes.
◆ Prediction
Multi-tenancy graduating from experimental remains the likely next milestone as it pairs with reduced-privilege deployments. Whether GPU telemetry gets gadget consumers soon 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 Inspektor Gadget 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 Inspektor Gadget 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 Inspektor Gadget alternatives → · See all runc alternatives →
Recent activity from Inspektor Gadget and runc
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 26d agoruncRelease candidate lifts 1024-CPU limit, removes deprecated APIs
- 27d agoInspektor Gadgetv0.57.0: rootless ig run and reduced-privilege deploys
- 1mo agoInspektor Gadgetv0.56.2: bounded owner reference enrichment
- 1mo agoInspektor Gadgetv0.56.1 hardens USDT parsing against crafted binaries
- 1mo agoruncWorkaround for kernel bug that crashed runc on cgroup v2
- 1mo agoInspektor GadgetRelease v0.56.0 ⚡
- 2mo agoInspektor GadgetRelease v0.55.1
- 3mo agoInspektor GadgetRelease v0.55.0 ⚡
- 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 Inspektor Gadget and runc?
They serve adjacent needs but don't currently overlap on shipped themes. Inspektor Gadget and runc are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Inspektor Gadget better than runc?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Inspektor Gadget and runc are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Inspektor Gadget?
Top Inspektor Gadget alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Inspektor Gadget alternatives" section above for the current picks, or visit /alternatives/inspektor-gadget 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.