Apache Druid
Druid 38 drops Java 17, recommends Java 25 and took longer to arrive than its predecessors
Comparison · Infra & APIs
CircleCI vs runc
A side-by-side editorial comparison of CircleCI and runc — release velocity, themes, recent moves, and the top alternatives to consider.
CircleCI vs runc: at a glance
What is CircleCI?
CircleCI Server 4.10.2 and 4.9.7 carry the eMudhra distrust to self-hosted installs.
CircleCI spent late October on two surfaces. In the cloud product, GitHub check runs now explain on-hold jobs and re-runs run as the person who clicked, and CLI 1.11 can script Slack notifications. On Oct 28, Server 4.10.2 and 4.9.7 stopped trusting the compromised eMudhra intermediates and fixed Details links, proxy-related 500s and a tracing crash loop. Vault is deprecated and will be unsupported in Server 5.0, with a script to migrate to Tink.
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.
CircleCI vs runc: editorial side-by-side
CircleCI
7.5INFRA · APIS
CircleCI Server 4.10.2 and 4.9.7 carry the eMudhra distrust to self-hosted installs.
◆ Current state
CircleCI spent late October on two surfaces. In the cloud product, GitHub check runs now explain on-hold jobs and re-runs run as the person who clicked, and CLI 1.11 can script Slack notifications. On Oct 28, Server 4.10.2 and 4.9.7 stopped trusting the compromised eMudhra intermediates and fixed Details links, proxy-related 500s and a tracing crash loop. Vault is deprecated and will be unsupported in Server 5.0, with a script to migrate to Tink.
◆ Where it's heading
The platform keeps pulling identity and permission checks onto the real actor: scoped tokens, V3 OIDC claims and re-run attribution. The self-hosted line follows with its own permission and link repairs. Server 5.0 is taking shape as a breaking release, at least for secret storage.
◆ Prediction
Expect more Server 4.x patches ahead of 5.0, with Tink migration guidance repeated until Vault support ends.
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 CircleCI 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 CircleCI 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 CircleCI alternatives → · See all runc alternatives →
Recent activity from CircleCI and runc
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4d agoCircleCIServer 4.10.2 distrusts eMudhra CAs, fixes context permissions
- 4d agoCircleCIServer 4.9.7 distrusts eMudhra CAs, fixes tracing crash loop
- 9d agoCircleCIGitHub check re-runs now run as the user who clicked Re-run
- 9d agoCircleCIImproved GitHub check-run summaries for on-hold workflows
- 10d agoCircleCIXcode 27.2 RC 1 Available
- 10d agoCircleCIManage a project’s Slack notifications from the CLI
- 26d agoruncRelease candidate lifts 1024-CPU limit, removes deprecated APIs
- 1mo agoruncWorkaround for kernel bug that crashed runc on cgroup v2
- 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 CircleCI and runc?
They serve adjacent needs but don't currently overlap on shipped themes. CircleCI is currently shipping more aggressively (velocity 7.5 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 CircleCI better than runc?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. CircleCI is currently shipping more aggressively (velocity 7.5 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 CircleCI?
Top CircleCI alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "CircleCI alternatives" section above for the current picks, or visit /alternatives/circleci 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.