Inspektor Gadget
Inspektor Gadget keeps cutting the privileges an eBPF tool has to ask for.
Comparison · Infra & APIs
Lima vs runc
A side-by-side editorial comparison of Lima and runc — release velocity, themes, recent moves, and the top alternatives to consider.
Lima vs runc: at a glance
What is Lima?
Lima 2.3 nears release, with a Windows path that drops QEMU and a new TUI
Lima v2.3.0-rc.0 is out with an experimental HCS driver that removes the QEMU dependency on Windows hosts, block device attachment for VZ guests on macOS, and experimental shared, host and bridged networks on Linux hosts. limactl menu adds a menu-based interface, which now opens when limactl runs on a terminal without arguments. The default Ubuntu template moves to 26.10.
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.
Lima vs runc: editorial side-by-side
Lima
5.0INFRA · APIS
Lima 2.3 nears release, with a Windows path that drops QEMU and a new TUI
◆ Current state
Lima v2.3.0-rc.0 is out with an experimental HCS driver that removes the QEMU dependency on Windows hosts, block device attachment for VZ guests on macOS, and experimental shared, host and bridged networks on Linux hosts. limactl menu adds a menu-based interface, which now opens when limactl runs on a terminal without arguments. The default Ubuntu template moves to 26.10.
◆ Where it's heading
The any-guest, any-host direction now reaches all three desktop platforms in one release, and each host gets a feature suited to its own virtualization stack. The menu interface is a different kind of addition: it aims at people who do not want to memorize the CLI. LFX mentees and outside contributors continue to carry much of this work, and the project's experimental-first labeling still applies to the biggest items.
◆ Prediction
A 2.3.0 final is the next step after rc.0. The HCS driver and Linux network modes should stay experimental there, following the pattern earlier platform additions took.
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 Lima 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 Lima or runc.
k0s
k0s opens its 1.37 line while security fixes ride the older branches.
Grype
Grype widens distro accuracy while each release clears its own dependency advisories.
BorgBackup
Borg 2.0 beta 25 breaks repositories to swap its hash and repository format.
CrowdSec
CrowdSec's 1.8.2 candidates let operators write their own bot fingerprints.
AdGuard Home
AdGuard Home renames its next release: the 0.108 beta line becomes v1.0.0.
Recent activity from Lima and runc
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoLima2.3.0-rc.0: HCS on Windows, VZ block devices, limactl menu
- 26d agoruncRelease candidate lifts 1024-CPU limit, removes deprecated APIs
- 29d agoLima2.3.0-beta.1: VZ block devices and native Windows OpenSSH
- 1mo agoruncWorkaround for kernel bug that crashed runc on cgroup v2
- 2mo agoLima2.3.0-beta.0: an experimental HCS driver for Windows hosts
- 3mo agoLima2.2.0-rc.0: Windows 11 guests and a sudo opt-out
- 3mo agorunctmpfs regression on Ubuntu 20.04 kernels fixed
- 4mo agoLima2.2.0-beta.0: Windows Server 2025 guests and TPM emulation
- 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
- 6mo agoLima2.1.2-beta.0: CLI mount and rsync path fixes
Frequently asked questions
What is the difference between Lima and runc?
They serve adjacent needs but don't currently overlap on shipped themes. Lima 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 Lima better than runc?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Lima 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 Lima?
Top Lima alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Lima alternatives" section above for the current picks, or visit /alternatives/lima 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.