Skip to main content
Lexicon
Lexicon
Containerd

Containerd

Difficulty: Intermediate
4 min read
Updated 2026-08-21

In plain English

Plain definition

Containerd is a program that runs on a server and does the actual work of starting, stopping and managing containers. Higher-level tools such as Kubernetes or Docker tell Containerd what to run, and Containerd carries out the low-level work of pulling container images, preparing the filesystem and supervising the running processes.

What Containerd does on a host

On each host, Containerd covers the complete container lifecycle: image transfer and storage, container execution and supervision, low-level storage and network attachments, and other host-level operations. It exposes all of this through a gRPC API and typically delegates the creation of the isolated process itself to an OCI-compliant lower-level runtime such as runc, using the containerd-shim process to keep each container supervised independently of the main Containerd daemon.

Who talks to Containerd

End users rarely operate Containerd directly. It sits underneath higher-level orchestration and developer tooling. On a Kubernetes node, the kubelet communicates with Containerd through the Container Runtime Interface (CRI) to create and manage pod containers. On a workstation, tools such as Docker or nerdctl issue the same kind of lifecycle calls. What you can see of Containerd typically comes from its own logs, its CLI client (ctr, intended mainly for debugging), and the higher-level tool’s status output rather than from direct end-user interaction.

Its place in the container stack

Containerd occupies the middle layer of the container stack. Above it sit orchestrators and developer-facing tools (Kubernetes, Docker, nerdctl) that decide what should run and where. Below it sits the OCI runtime specification and runtimes such as runc that perform the actual namespace and cgroup isolation using Linux kernel primitives. Containerd connects the two: it accepts lifecycle requests through its API, manages image and snapshot storage, and hands off process creation to the lower-level runtime while retaining supervisory responsibility for the resulting container.

Containerd on a Kubernetes node

A Kubernetes node running Containerd as its configured container runtime will show a containerd process on the host, alongside per-container containerd-shim processes. The kubelet configuration shows the CRI socket path used to reach Containerd, and Containerd’s own logs record image pulls and container lifecycle events independently of what kubectl reports at the cluster level.

Containerd is not Docker

Containerd is often treated as the same thing as Docker. Docker is a broader developer-facing toolset that, for its container execution, itself relies on Containerd internally. Containerd on its own does not provide image building, a full CLI aimed at end users, or Compose-style multi-container orchestration. It is a runtime component rather than a complete developer platform.

Terms that sit next to Containerd

  • OCI runtime specification
  • runc
  • Container Runtime Interface (CRI)
  • Kubernetes kubelet
  • Docker

Further Reading

The official Containerd documentation has the authoritative detail on API structure, snapshotter plugins and CRI integration. Check any version-specific configuration behaviour against the documentation revision matching the deployed release before making operational changes.

About this page

Credited to

Dates

Published

Corrections

No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.

Was this useful?

Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.