containerd

containerd is an open-source container runtime project focused on the core lifecycle operations required to run containers reliably. It manages image transfer and storage, container creation, execution, supervision, networking integration, and runtime interaction while leaving higher-level orchestration and developer workflow concerns to other systems. The project is widely used as a foundational component in cloud-native infrastructure, especially in Kubernetes clusters and managed container platforms. The project originated inside Docker as part of an effort to separate the low-level container execution engine from Docker's broader application and developer experience. Docker announced containerd in 2015 as an independent core component intended to provide a stable, reusable runtime layer. In 2017, Docker donated containerd to the Cloud Native Computing Foundation, placing the project within a neutral open-source governance environment alongside Kubernetes and other cloud-native technologies. containerd subsequently became a standalone CNCF project and reached graduated status in 2019. Its architecture is deliberately modular. The daemon exposes APIs and uses plugins for capabilities such as image distribution, content storage, snapshotters, metadata, runtime integration, and networking-related functions. OCI-compatible images and runtimes are central to its interoperability model. The project commonly uses runc as a default low-level runtime, while supporting alternative runtimes through its runtime interface. Kubernetes interacts with containerd through the Container Runtime Interface, allowing Kubernetes nodes to run containers without requiring the complete Docker Engine stack. containerd is not primarily marketed as an end-user application. Its users are platform engineers, cloud providers, Linux distributors, Kubernetes operators, enterprise infrastructure teams, and developers building container platforms. It is embedded or offered as a runtime component by multiple commercial and open-source products, including Kubernetes distributions and managed container services. This embedded role means the brand is often less visible to end users than the platforms built on top of it, although it is a major infrastructure dependency. The project is governed through open-source community processes under the CNCF. Its development, releases, documentation, security response, and ecosystem relationships are maintained by contributors from Docker, cloud providers, infrastructure vendors, Linux distributors, and independent engineering teams. There is no separately disclosed corporate headquarters, public stock listing, or conventional executive leadership structure for the project itself. Its present positioning is that of a neutral, portable, production-grade container runtime and an essential building block for cloud-native computing.

containerd developed from Docker's need for a focused, reusable core runtime. Docker announced the project in 2015 as an effort to extract the essential container-management functions from the broader Docker Engine and make them available to other platforms. The design separated low-level tasks such as image handling, filesystem snapshots, container process supervision, and runtime invocation from higher-level concerns including image builds, developer commands, application packaging, and orchestration. This separation became increasingly important as container technology expanded beyond the Docker product ecosystem. Cloud providers, Linux distributions, Kubernetes users, and infrastructure vendors wanted a runtime that could be embedded without adopting every component of Docker Engine. containerd's use of open interfaces and OCI-compatible image and runtime standards made it suitable for this role. Its daemon-based architecture also provided a stable service boundary for tools that needed to create and manage containers. In March 2017, Docker donated containerd to the Cloud Native Computing Foundation. The donation placed the project under a neutral foundation associated with Kubernetes and other cloud-native technologies. It also enabled broader technical participation and helped establish containerd as a general-purpose infrastructure project rather than a Docker-only implementation. Around this period, the project continued to mature its plugin model, image distribution support, snapshotter abstractions, runtime integration, and operational tooling. The release of containerd 1.0 in 2017 marked an important stabilization point. Kubernetes subsequently adopted containerd as a major runtime option through the Container Runtime Interface. This relationship became more significant when Kubernetes deprecated and later removed its direct dependency on the Docker Engine integration known as dockershim. That transition did not make Docker images obsolete: containerd continues to work with OCI and Docker-compatible images, while providing the runtime services needed by Kubernetes nodes. The CNCF announced containerd's graduation in 2019. Graduation signaled that the project had demonstrated sustained production use, an active and diverse community, documented governance, and a mature technical foundation. Later release lines expanded functionality and operational reliability. containerd 1.6, released in 2021, became an important long-term branch for production deployments, while subsequent releases continued improvements in runtime support, image management, plugin behavior, and platform compatibility. containerd 2.0 was released in 2024 as a new major version. The release represented an evolution of the project's APIs, plugin lifecycle, and supported integrations rather than a change in its basic mission. Across its history, containerd has remained deliberately narrow in scope: it supplies core container lifecycle infrastructure instead of attempting to replace orchestration systems, container build tools, registries, or complete developer platforms. Today, containerd operates as a CNCF-hosted open-source project with contributors from across the cloud-native ecosystem. It is used directly by infrastructure teams and indirectly through Kubernetes distributions, managed Kubernetes services, container platforms, and Linux software packages. Its importance comes less from consumer recognition than from its position in the software supply chain: it is a common runtime layer connecting container images, operating systems, low-level runtimes, and orchestration systems.

1. 2024containerd 2.0

   The project released its 2.0 major version with updated interfaces and plugin behavior while preserving its role as a core container runtime.

   Source
2. 2021containerd 1.6 line

   The 1.6 release line continued production adoption and expanded runtime, image, plugin, and platform capabilities.

   Source
3. 2019CNCF graduation

   containerd graduated from the CNCF incubation process after demonstrating maturity, adoption, governance, and community health.

   Source
4. 2017Donation to the CNCF

   Docker donated containerd to the Cloud Native Computing Foundation for neutral governance and broader ecosystem collaboration.

   Source
5. 2017containerd 1.0

   The first 1.0 release established a stable production-oriented runtime foundation and plugin architecture.

   Source
6. 2015Docker introduces containerd

   Docker announced containerd as a focused core container runtime intended to be reusable outside the complete Docker Engine product.

   Source

A neutral, open-source, production-grade container runtime and core infrastructure layer for Kubernetes, cloud platforms, and container tooling.

• containerd daemonContainer runtime2015

  The main containerd service manages container images, metadata, snapshots, container processes, and runtime connections. It provides the core daemon and API surface used by higher-level tools and orchestration platforms.

• CRI pluginKubernetes integration

  The Container Runtime Interface plugin allows Kubernetes kubelets to use containerd as their node runtime. It translates Kubernetes runtime operations into containerd services and integrates image and pod sandbox management.

• containerd-shimRuntime process management

  The shim architecture keeps container processes managed independently from the main daemon, helping preserve running workloads across daemon events and allowing different runtime implementations to integrate with containerd.

• Snapshotter frameworkContainer filesystem storage

  Snapshotters provide pluggable filesystem-layer storage for container images and writable container filesystems. The abstraction supports different storage technologies and deployment requirements.

• 2024Release of containerd 2.0Generation change

  The project needed a new major-version line to evolve APIs, plugin behavior, and supported integrations.

  What changed. The community released containerd 2.0.

  Aftermath. The new major version continued containerd's role as a production runtime while establishing a new compatibility and maintenance baseline.

  Source
• 2019CNCF graduationStrategy

  containerd had developed broad production adoption and an established contributor and governance model.

  What changed. The CNCF graduated containerd from incubation.

  Aftermath. Graduation reinforced containerd's position as a stable, vendor-neutral infrastructure layer.

  Source
• 2017Move containerd to neutral CNCF governanceM&A

  Docker's runtime component was increasingly relevant to projects and vendors beyond Docker's own product stack.

  What changed. Docker donated containerd to the Cloud Native Computing Foundation as an open-source project.

  Aftermath. The project gained neutral foundation governance and became a widely reusable component of the cloud-native ecosystem.

  Source

• 2024containerd 2.0 released

  The 2.0 release introduced a new major-version line with updated APIs and plugin behavior while continuing the project's role as a container runtime foundation.

  Product launchProduct generation
  Source
• 2019containerd achieves CNCF graduation

  The CNCF announced containerd's graduation after the project met the foundation's technical, community, governance, and adoption criteria.

  Other
  Source
• 2017Docker donates containerd to the Cloud Native Computing Foundation

  Docker contributed containerd to the CNCF, creating a neutral governance home for the container runtime and broadening participation in its development.

  M&A
  Source

1. containerd official website
2. containerd releases
3. Docker donates containerd to the Cloud Native Computing Foundation
4. containerd graduates from the Cloud Native Computing Foundation
5. containerd GitHub repository