Let's Try All the CRI Runtimes: Part 2: Answering the Why Question!
Talkat KubeCon + CloudNativeCon North America 2019 · on Wednesday, 2019-11-20· at 16:25· Room 1AB - San Diego Convention Center, Upper Level·
summary
Compares Docker, containerd and cri-o plus sandboxes Kata, Firecracker and gVisor and explains why each is chosen: Docker stays dominant for compatibility and tooling, containerd wins for a smaller footprint and shim API extensibility used by clouds (IBM, Google, Alibaba), cri-o aligns with RHEL/OpenShift and OCI libraries, Kata and Firecracker provide hypervisor isolation (Firecracker is microVM‑focused with narrow features), gVisor implements syscalls in userspace for sandboxing, Nabla requires rebuilt images and Singularity targets HPC. Demos run via RuntimeClass and kubelet CRI settings; storage experiments use device mapper snapshotter.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:16Again with the runtimes talk!?
- 4:02Background: CRI Runtimes
- 5:35Where are we?
- 7:09Docker: Why
- 10:56Containerd: What
- 15:07CRI-O: What
- 20:21Isolators
- 23:17Kata Containers: What
- 25:46AWS Firecracker: What
- 28:18gVisor: What
- 30:56Nabla: What and Why
- 31:46Singularity: What and Why
- 32:33Summary
related talks
34mLet's Try Every CRI Runtime Available for Kubernetes. No, Really!
24mOCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes
35mWhat Container Runtime Do I Need?
23mOCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes - Phil Estes, IBM
46mCRI-O: All the Runtime Kubernetes need
42mCRI Runtimes Deep Dive: Who's Running My Kubernetes Pod!?
33mCRI-O Still Loves Kubernetes
29mCRI-O: All the Runtime Kubernetes Needs, and Nothing More