Apache Druid
Druid 38 drops Java 17, recommends Java 25 and took longer to arrive than its predecessors
Comparison · Infra & APIs
runc vs Tekton Pipelines
A side-by-side editorial comparison of runc and Tekton Pipelines — release velocity, themes, recent moves, and the top alternatives to consider.
runc vs Tekton Pipelines: at a glance
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.
What is Tekton Pipelines?
Tekton 1.18 LTS lets a Task finish its steps and still fail.
v1.18.0, an LTS release, adds continueAndFail for step.onError: remaining steps run, then the TaskRun fails. Controller-managed labels become immutable through the webhook, and a truncation bug in large OCI-resolved bundles is fixed. On October 23 five maintained branches, from v1.6.x to v1.17.x, received the same Go 1.27.3 image bump, and v1.6, v1.9 and v1.12 also got a vendor tarball fix.
runc vs Tekton Pipelines: editorial side-by-side
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.
Tekton Pipelines
5.0INFRA · APIS
Tekton 1.18 LTS lets a Task finish its steps and still fail.
◆ Current state
v1.18.0, an LTS release, adds continueAndFail for step.onError: remaining steps run, then the TaskRun fails. Controller-managed labels become immutable through the webhook, and a truncation bug in large OCI-resolved bundles is fixed. On October 23 five maintained branches, from v1.6.x to v1.17.x, received the same Go 1.27.3 image bump, and v1.6, v1.9 and v1.12 also got a vendor tarball fix.
◆ Where it's heading
This cycle is quieter than the security-context change in v1.16. New capability is small and aimed at real pipeline behavior, such as collecting all test results before failing, while most of the release effort goes to keeping many branches current. Making labels immutable fits the same theme as v1.16: tightening what users can change on objects the controller owns.
◆ Prediction
Expect more same-day patch sets across the LTS branches, since that pattern now repeats. No further end-of-life move appears in these entries, so timing for retiring older branches is unclear.
Alternatives to runc and Tekton Pipelines
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 Tekton Pipelines.
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 runc alternatives → · See all Tekton Pipelines alternatives →
Recent activity from runc and Tekton Pipelines
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3d agoTekton PipelinesTekton 1.18 LTS adds continueAndFail for failing steps
- 9d agoTekton Pipelinesv1.6.8: Go 1.27.3 image and vendor tarball fix
- 9d agoTekton Pipelinesv1.12.3: Go 1.27.3 image and crypto dependency update
- 9d agoTekton Pipelinesv1.9.9: Go 1.27.3 image and crypto dependency update
- 9d agoTekton Pipelinesv1.15.5: Go 1.27.3 image and crypto dependency update
- 9d agoTekton Pipelinesv1.17.1: Go 1.27.3 image bump
- 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 runc and Tekton Pipelines?
They serve adjacent needs but don't currently overlap on shipped themes. Tekton Pipelines 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 runc better than Tekton Pipelines?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Tekton Pipelines 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 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 Tekton Pipelines?
Top Tekton Pipelines alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Tekton Pipelines alternatives" section above for the current picks, or visit /alternatives/tekton for the full list with editorial commentary on each.