← Back to home
Comparison · Infra & APIs

runc vs Velociraptor

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

runc vs Velociraptor: at a glance

FeatureruncVelociraptor
SectorInfra & APIsInfra & APIs
Velocity score5.00.0
Sparks · 30d00
Top themescontainer runtime, security, checkpoint restore, release candidatedfir, endpoint-security, open-source, security-patches
Last editorial update1d ago8h ago
WebsiteVisit →Visit →

What is runc?

runc patches one restore bug across four release lines at once.

runc shipped 1.5.3, 1.4.4, 1.3.7 and 1.6.0-rc.2 on the same day, all fixing CVE-2026-119101: a crafted image could make runc restore bind-mount any host directory into a restored container, read-write. Only people who checkpoint and later restore untrusted containers as root are exposed. The 1.6.0 candidate also changes how mount destinations that start with the rootfs path are read, following the runtime spec literally.

Read the full runc trajectory →

What is Velociraptor?

Velociraptor's recent releases are mostly about patching CVEs.

Velociraptor 0.77.3 shipped on October 5 as a bug fix and CVE release; it also adds an artifact that uploads server results to Azure Monitor and trims the columns emitted by the backup artifacts. 0.77.2 and a 0.76.7 backport in September and August were CVE fixes. The 0.77.1 feature release landed in June, but its notes in the feed only link out.

Read the full Velociraptor trajectory →

runc vs Velociraptor: editorial side-by-side

R
runc
INFRA · APIS
5.0

runc patches one restore bug across four release lines at once.

◆ Current state

runc shipped 1.5.3, 1.4.4, 1.3.7 and 1.6.0-rc.2 on the same day, all fixing CVE-2026-119101: a crafted image could make runc restore bind-mount any host directory into a restored container, read-write. Only people who checkpoint and later restore untrusted containers as root are exposed. The 1.6.0 candidate also changes how mount destinations that start with the rootfs path are read, following the runtime spec literally.

◆ Where it's heading

The project now maintains four supported branches and backports security work to each one in lockstep, while 1.6.0 keeps trading quiet tolerance for strict spec behaviour: refused read-only configs in rc.1, literal mount paths in rc.2. Users relying on runc's old lenient handling will feel 1.6.0 more than any feature it adds.

◆ Prediction

Expect 1.6.0 final after one more candidate, with 1.3.z ending since 1.3.7 is labelled the probable last patch.

V
Velociraptor
INFRA · APIS
0.0

Velociraptor's recent releases are mostly about patching CVEs.

◆ Current state

Velociraptor 0.77.3 shipped on October 5 as a bug fix and CVE release; it also adds an artifact that uploads server results to Azure Monitor and trims the columns emitted by the backup artifacts. 0.77.2 and a 0.76.7 backport in September and August were CVE fixes. The 0.77.1 feature release landed in June, but its notes in the feed only link out.

◆ Where it's heading

Since June the project has been in security mode, fixing CVEs on the current line and backporting to the previous one. Feature work shows up as new artifacts, here an Azure Monitor export, which keeps Velociraptor feeding results into the logging tools teams already use.

◆ Prediction

Expect further 0.77 patch releases and possibly another backport if new CVEs are published; the timing of a 0.78 feature release is not signaled here.

Alternatives to runc and Velociraptor

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

See all runc alternatives → · See all Velociraptor alternatives →

Recent activity from runc and Velociraptor

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

  1. 2d agoruncCVE-2026-119101 fix for checkpoint/restore in the 1.5 line
  2. 2d agoruncSecond 1.6.0 candidate: restore CVE fix, literal mount paths
  3. 2d agorunc1.4 line gets the restore CVE fix and cgroup v2 crash workaround
  4. 2d agoruncLikely final 1.3 patch carries the restore CVE fix
  5. 1mo agoruncRelease candidate lifts 1024-CPU limit, removes deprecated APIs
  6. 1mo agoVelociraptorVelociraptor 0.77.3 fixes CVEs and adds Azure Monitor upload
  7. 1mo agoVelociraptorVelociraptor 0.77.2 patches published CVEs
  8. 1mo agoruncWorkaround for kernel bug that crashed runc on cgroup v2
  9. 3mo agoVelociraptorVelociraptor 0.76.7 backports CVE fixes
  10. 4mo agoVelociraptorVelociraptor 0.77.1 feature release ships
  11. 5mo agoVelociraptorVelociraptor 0.77.1 RC1 opens for testing
  12. 5mo agoVelociraptorVelociraptor 0.76.6 bug fix release

Frequently asked questions

What is the difference between runc and Velociraptor?

They serve adjacent needs but don't currently overlap on shipped themes. runc is currently shipping more aggressively (velocity 5.0 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 runc better than Velociraptor?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. runc is currently shipping more aggressively (velocity 5.0 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 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.

What are the best alternatives to Velociraptor?

Top Velociraptor alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Velociraptor alternatives" section above for the current picks, or visit /alternatives/velociraptor for the full list with editorial commentary on each.