← Back to home
Comparison · Infra & APIs

Incus vs runc

A side-by-side editorial comparison of Incus and runc — release velocity, themes, recent moves, and the top alternatives to consider.

Incus vs runc: at a glance

FeatureIncusrunc
SectorInfra & APIsInfra & APIs
Velocity score5.02.5
Sparks · 30d00
Top themescontainer manager, live migration, sr-iov, project isolationcontainer runtime, release candidate, breaking changes, kernel workaround
Last editorial update2h ago2h ago
WebsiteVisit →Visit →

What is Incus?

Incus 7.6 fixes 18 security issues, eight critical, and adds SR-IOV NIC live migration

Incus 7.6, released October 30, carries 18 security fixes, eight rated critical, many of them about restricted projects reaching the default project or the host, plus an authentication bypass through unverified client certificate chains. Its features aim at larger environments: live migration for VMs using SR-IOV NICs, multifd for VM live migration, cluster healing options, compression for block volumes, and OIDC opaque tokens. 7.5 before it added live migration between projects, cluster metrics and NVIDIA GPU cliques. The 7.0 LTS branch received a second patch, 7.0.2, with no described changes.

Read the full Incus trajectory →

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.

Read the full runc trajectory →

Incus vs runc: editorial side-by-side

I
Incus
INFRA · APIS
5.0

Incus 7.6 fixes 18 security issues, eight critical, and adds SR-IOV NIC live migration

◆ Current state

Incus 7.6, released October 30, carries 18 security fixes, eight rated critical, many of them about restricted projects reaching the default project or the host, plus an authentication bypass through unverified client certificate chains. Its features aim at larger environments: live migration for VMs using SR-IOV NICs, multifd for VM live migration, cluster healing options, compression for block volumes, and OIDC opaque tokens. 7.5 before it added live migration between projects, cluster metrics and NVIDIA GPU cliques. The 7.0 LTS branch received a second patch, 7.0.2, with no described changes.

◆ Where it's heading

Live migration is still the through-line: 7.4 made it near-live for dependent disks, 7.5 took it across projects, and 7.6 extends it to VMs using SR-IOV NICs. The other thread is multi-tenancy under scrutiny. The size of the 7.6 security batch, with several critical items in project isolation, shows that restricted projects are now being tested as a real boundary, and the release adds a build and threat model for Anthropic's OSS Scanner.

◆ Prediction

Expect a 7.6.x patch or further security fixes, because the project-isolation findings cover a wide surface. The monthly feature cadence should continue with more live-migration throughput work, given multifd and the throughput improvements in this release.

R
runc
INFRA · APIS
2.5

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 Incus 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 Incus or runc.

See all Incus alternatives → · See all runc alternatives →

Recent activity from Incus and runc

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 2d agoIncus18 security fixes, SR-IOV NIC live migration and multifd
  2. 16d agoIncusSecond patch on the 7.0 LTS branch
  3. 26d agoruncRelease candidate lifts 1024-CPU limit, removes deprecated APIs
  4. 1mo agoruncWorkaround for kernel bug that crashed runc on cgroup v2
  5. 1mo agoIncusLive migration across projects, cluster metrics, NVIDIA GPU cliques
  6. 2mo agoIncusIncus 7.4 adds near-live migration and Secure Boot key management ⚡
  7. 3mo agoIncusNative Windows and macOS installers; QMP command timeouts
  8. 3mo agorunctmpfs regression on Ubuntu 20.04 kernels fixed
  9. 3mo agoIncusFirst patch release on the 7.0 LTS branch
  10. 4mo agoruncrunc 1.5.0 stable, with dated support windows for older branches
  11. 4mo agoruncCVE-2026-41579: /dev symlink host write access fixed
  12. 4mo agoruncRelease candidate carrying the CVE-2026-41579 fix

Frequently asked questions

What is the difference between Incus and runc?

They serve adjacent needs but don't currently overlap on shipped themes. Incus 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 Incus better than runc?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Incus 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 Incus?

Top Incus alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Incus alternatives" section above for the current picks, or visit /alternatives/incus 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.