Five things you need to know about your container runtime
summary
Focuses on the runtime actually in use: containerd as the common CRI implementation that delegates to runC, relies on the OCI specs for image and runtime portability, and supports pluggable snapshots and shims. Notes working lazy‑loading projects like Sochi and GKE image streaming, a wasm path via runw, and built‑in Prometheus metrics plus OpenTelemetry tracing of image pulls. Config details include host.toml registry files and a containerd 2.0 config migration helper. Community has 24 maintainers from 13 employers collaborating since 2016.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 4:22What is a container runtime
- 7:11Runtime interchangeability
- 11:04Extensibility of runtimes
- 16:29Runtime observability
- 20:29Configuring runtimes
- 23:19Runtime ecosystem collaboration
- 26:30Takeaways
- 27:35Q&A
related talks
24mOCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes
23mOCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes - Phil Estes, IBM
35mWhat Container Runtime Do I Need?
01h 17mIntro + Deep Dive: containerd
34mContainer Runtime Evolving in Kubernetes
46mCRI-O: All the Runtime Kubernetes need
34mContainer Runtime Evolving in Kubernetes
42mCRI Runtimes Deep Dive: Who's Running My Kubernetes Pod!?
