There is one daemon that almost every Kubernetes node on earth runs, that Docker itself now builds on, that Amazon, Google, and Microsoft all ship as the default container runtime — and it started as a Docker employee's side project to control a different tool. containerd's story is the story of how the container ecosystem's "boring plumbing" became its most load-bearing layer, survived the company that founded it losing the orchestrator war, absorbed Kubernetes' garbage-collected runtime interface, and in 2026 found out what happens when a decade-old daemon carries too many features: a security crisis that ended with the project deleting its own checkpointing feature and patching five release branches at once.

The Origin: Plumbing Docker Didn't Want to Be

A daemon to control runC (2015)

containerd begins, as half the container ecosystem does, with Michael Crosby. The git archaeology is unusually clean: the repository was created on , and the deepest commit page reads:

# Deepest page of containerd/containerd commit history:
$ gh api "repos/containerd/containerd/commits?until=2015-12-08T00:00:00Z&per_page=100"

DATE        SHA         AUTHOR          MESSAGE
2015-11-05  15a96783ca  Michael Crosby  Initial commit
2015-11-05  05683fb0ee  Michael Crosby  Fix build errors
2015-11-06  2af0f297fe  Michael Crosby  Add basic counters
2015-11-06  5f5f4904e0  Michael Crosby  Making containers run and delete
2015-11-06  1005dfb224  Michael Crosby  Fix panic on nil container

# One author, eight days of evening-mode commits, "Making containers
# run and delete" — a runtime manager being sketched in public.