What Container Runtime Do I Need?
Talkat KubeCon + CloudNativeCon North America 2022 · on Thursday, 2022-10-27· at 15:25· Virtual Platform Only·
summary
Explains why the choice of runtime depends on constraints: containerd + runc handle image lifecycle and low‑level process creation via Linux namespaces, cgroups and chroot; Kubernetes uses the CRI to plug in any OCI runtime; podman (daemonless) is a drop‑in Docker replacement that runs rootless pods; sandbox runtimes like gVisor, Kata and Firecracker provide VM‑level isolation for higher security. Recommends Docker for simple dev use, containerd for cluster lifecycle, sandbox runtimes for regulated workloads.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:51What are Containers?
- 11:12Under the hood (chroot)
- 13:55Under the hood (cgroups)
- 18:11Open Container Initiative (OCI)
- 19:56Container Runtime/Tools (High Level)
- 23:52Container Runtimes (Low Level)
- 25:13Container Runtimes (Sandboxed)
- 26:50Container Runtime Usecases
related talks
24mOCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes
34mContainer Runtime Evolving in Kubernetes
34mContainer Runtime Evolving in Kubernetes
23mOCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes - Phil Estes, IBM
37mLet's Try All the CRI Runtimes: Part 2: Answering the Why Question!
43mIntro: containerd
34mLet's Try Every CRI Runtime Available for Kubernetes. No, Really!
42mCRI Runtimes Deep Dive: Who's Running My Kubernetes Pod!?
