Docker Donates containerd to the Cloud Native Computing Foundation
Accepted as an incubating CNCF project on March 29, 2017, containerd split out the core container-runtime functionality from Docker itself — becoming the shared runtime foundation much of the ecosystem, including Kubernetes, later standardized on.
containerd — the core container runtime functionality underneath Docker — was accepted by the CNCF’s Technical Oversight Committee as an incubating project on March 29, 2017, after Docker spun it out as a standalone open-source project in December 2016 with the explicit intention of donating it to a neutral foundation.
What containerd actually is
containerd handles the bare-bones runtime operations a container needs — pulling images, managing container lifecycle, handling storage and network namespaces — the specific slice of “run a container” functionality that sits beneath higher-level tools like the Docker CLI or Kubernetes’ own orchestration layer.
Why Docker split it out at all
By 2016, Docker’s own platform had grown well beyond just running containers — orchestration, networking, image building, a CLI, and more were all bundled into one project. Extracting containerd isolated the specific, reusable runtime piece other tools and orchestrators could depend on directly, without needing all of Docker’s other components along with it.
The path to graduation
containerd reached general availability at version 1.0 in December 2017, and the CNCF announced its graduation — the foundation’s highest maturity tier — in February 2019, alongside Kubernetes and Prometheus among the small set of projects that had reached that status at the time.
Why this mattered for the broader container ecosystem
Donating containerd to a neutral foundation, rather than keeping it as a Docker-controlled dependency, meant other projects — including Kubernetes itself, which eventually adopted containerd directly as a supported container runtime — could depend on it without being tied to Docker’s own product roadmap or governance. It’s a clear example of the same standards-and-neutrality dynamic behind the Open Container Initiative, applied to an actual runtime implementation rather than just a specification.
Sources: containerd joins the Cloud Native Computing Foundation — CNCF, containerd Project Journey Report — CNCF, General availability of containerd 1.0 is here! — CNCF