Apache Druid
Druid 38 drops Java 17, recommends Java 25 and took longer to arrive than its predecessors
Comparison · Infra & APIs
Dokploy vs runc
A side-by-side editorial comparison of Dokploy and runc — release velocity, themes, recent moves, and the top alternatives to consider.
Dokploy vs runc: at a glance
What is Dokploy?
Dokploy's 0.30 line lands as cloud billing and a Docker network UI, with quiet patches since.
This feed jumps from v0.29.14 to v0.30.10, dated October 22, a tag with no notes. The GitHub releases in between show v0.30.0 adding a Docker network management UI, then Cloud onboarding, billing and trial work in September. Before that, the 0.29 line added encrypted environment variables and closed a git clone command injection.
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.
Dokploy vs runc: editorial side-by-side
Dokploy
2.5INFRA · APIS
Dokploy's 0.30 line lands as cloud billing and a Docker network UI, with quiet patches since.
◆ Current state
This feed jumps from v0.29.14 to v0.30.10, dated October 22, a tag with no notes. The GitHub releases in between show v0.30.0 adding a Docker network management UI, then Cloud onboarding, billing and trial work in September. Before that, the 0.29 line added encrypted environment variables and closed a git clone command injection.
◆ Where it's heading
The commercial thread predicted from the plan limits has become concrete: the 0.30 releases include Cloud onboarding and trial handling alongside the self-hosted product. Hardening continues in smaller steps, including a Node.js security bump in v0.30.9. Patch notes have grown thinner, and two recent tags carry no change list at all.
◆ Prediction
Expect further Cloud billing and onboarding work on the 0.30 line. With v0.30.10's notes empty, its content cannot be judged.
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 Dokploy 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 Dokploy 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
See all Dokploy alternatives → · See all runc alternatives →
Recent activity from Dokploy and runc
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 10d agoDokployv0.30.10: tag with no release notes
- 26d agoruncRelease candidate lifts 1024-CPU limit, removes deprecated APIs
- 1mo agoruncWorkaround for kernel bug that crashed runc on cgroup v2
- 2mo agoDokployv0.29.14: fixes only, including Postgres argument-limit rewrites
- 3mo agoDokployv0.29.13 closes an OS command injection in git clone
- 3mo agorunctmpfs regression on Ubuntu 20.04 kernels fixed
- 3mo agoDokployv0.29.12 encrypts environment variables at rest with AES-256-GCM ⚡
- 3mo agoDokployv0.29.11 pins the install script to each release
- 3mo agoDokployv0.29.10 introduces plan limits
- 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 Dokploy and runc?
They serve adjacent needs but don't currently overlap on shipped themes. Dokploy 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 Dokploy better than runc?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Dokploy 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 Dokploy?
Top Dokploy alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dokploy alternatives" section above for the current picks, or visit /alternatives/dokploy 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.