Apache Druid
Druid 38 drops Java 17, recommends Java 25 and took longer to arrive than its predecessors
Comparison · Infra & APIs
Dagger vs runc
A side-by-side editorial comparison of Dagger and runc — release velocity, themes, recent moves, and the top alternatives to consider.
Dagger vs runc: at a glance
What is Dagger?
Dagger now runs the engines for you and reports CI per test, not per job.
Dagger's recent changelog holds two product moves. Cloud Engines, in September, are hosted engines with scale-out, distributed cache and observability, billed only for resources used, with Dagger claiming repeat work costs 5× less. Test-native CI, in October, tracks individual tests, so a failure names the test and only that test is run again. Around them sit cache and plumbing changes, including COPY steps that depend only on the files they copy and SSH-mounted remote filesystems.
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.
Dagger vs runc: editorial side-by-side
Dagger
2.5INFRA · APIS
Dagger now runs the engines for you and reports CI per test, not per job.
◆ Current state
Dagger's recent changelog holds two product moves. Cloud Engines, in September, are hosted engines with scale-out, distributed cache and observability, billed only for resources used, with Dagger claiming repeat work costs 5× less. Test-native CI, in October, tracks individual tests, so a failure names the test and only that test is run again. Around them sit cache and plumbing changes, including COPY steps that depend only on the files they copy and SSH-mounted remote filesystems.
◆ Where it's heading
Both moves rest on the same idea: treat the pipeline as a graph Dagger can see into, then avoid repeating work. A layer cache that survives unrelated file changes, per-test reruns and a distributed cache all reduce what a run must redo. Cloud Engines turn that saving into something sold, the one metered offering in these entries.
◆ Prediction
Expect Test-native CI and Cloud Engines to converge, with per-test reruns offered through hosted engines. That link is inferred from the two launches; the entries neither state it nor give pricing detail.
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 Dagger 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 Dagger or runc.
Okta
Okta adds TypeScript to its Cross App Access guides and dates the end of Classic Engine features
Gitness
Harness Open Source last shipped in August 2025, on this feed at least
Payload CMS
Payload's v4 beta ships every few days, and most of the risk sits in the breaking-change notes
Scalar
Scalar is testing demand for hosting from inside localhost
Incus
Incus 7.6 fixes 18 security issues, eight critical, and adds SR-IOV NIC live migration
Recent activity from Dagger and runc
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 11d agoDaggerTest-native CI
- 26d agoruncRelease candidate lifts 1024-CPU limit, removes deprecated APIs
- 1mo agoDaggerCloud Engines
- 1mo agoruncWorkaround for kernel bug that crashed runc on cgroup v2
- 2mo agoDaggerRemote filesystems over SSH
- 3mo agoDaggerDockerfile builds keep their layer cache
- 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
- 4mo agoDaggerUse a service as an image registry
- 5mo agoDaggerCross-language interfaces
Frequently asked questions
What is the difference between Dagger and runc?
They serve adjacent needs but don't currently overlap on shipped themes. Dagger 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 Dagger better than runc?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Dagger 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 Dagger?
Top Dagger alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dagger alternatives" section above for the current picks, or visit /alternatives/dagger 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.