Apache Druid
Druid 38 drops Java 17, recommends Java 25 and took longer to arrive than its predecessors
Comparison · Infra & APIs
Dokku vs runc
A side-by-side editorial comparison of Dokku and runc — release velocity, themes, recent moves, and the top alternatives to consider.
Dokku vs runc: at a glance
What is Dokku?
Dokku's autumn patches swap new features for safer deploys and stricter validation.
The 0.38 line reached v0.38.34 in late October, and the recent releases are mostly about correctness. Deploy locks now release on exit and honor apps:lock, app names and arguments are validated across commands, config write failures are reported, and dokku run propagates exit codes. Smaller additions include a --no-cache flag for ps:rebuild, per-entry cron MAILTO and a configurable nginx proxy HTTP version.
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.
Dokku vs runc: editorial side-by-side
Dokku
5.0INFRA · APIS
Dokku's autumn patches swap new features for safer deploys and stricter validation.
◆ Current state
The 0.38 line reached v0.38.34 in late October, and the recent releases are mostly about correctness. Deploy locks now release on exit and honor apps:lock, app names and arguments are validated across commands, config write failures are reported, and dokku run propagates exit codes. Smaller additions include a --no-cache flag for ps:rebuild, per-entry cron MAILTO and a configurable nginx proxy HTTP version.
◆ Where it's heading
The August k3s parity push has given way to a hardening pass through commands that used to fail quietly. A second thread makes configuration declarative: storage mounts, scheduler-k3s metadata and chart overrides each gained a whole-set form, which suits automation tools more than people at a terminal. Machine use of the CLI remains the through-line.
◆ Prediction
Expect the whole-set form to reach more properties, since three subsystems have now gained it. Patch releases should stay frequent, and the notes give no sign of a move past the 0.38 line.
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 Dokku 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 Dokku 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 Dokku and runc
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3d agoDokkuv0.38.34: ps:rebuild --no-cache and full network attachment
- 3d agoDokkuv0.38.33: wget dependency fix for source installs
- 8d agoDokkuv0.38.32: safer deploy locks, per-cron MAILTO, HAProxy TLS
- 26d agoruncRelease candidate lifts 1024-CPU limit, removes deprecated APIs
- 1mo agoDokkuv0.38.31: stricter validation; procfile shell operators removed
- 1mo agoruncWorkaround for kernel bug that crashed runc on cgroup v2
- 1mo agoDokkuv0.38.30: per-mount storage replace and sysctl reporting
- 1mo agoDokkuv0.38.29: whole-set config forms and honest exit codes
- 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 Dokku and runc?
They serve adjacent needs but don't currently overlap on shipped themes. Dokku 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 Dokku better than runc?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Dokku 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 Dokku?
Top Dokku alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dokku alternatives" section above for the current picks, or visit /alternatives/dokku 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.