containerd
summary
containerd’s architecture and plugin model enable building custom snapshotters and integrating alternate runtimes via CRI and a shim layer; shim v2 provides an abstraction used to integrate gVisor (and other sandboxes) so their special process/metrics behavior works with containerd. Kubernetes uses runtimeClass and a runtime+ API to pass runtime choice; benchmarks (105‑pod startup and management) show containerd outperforming the old Docker shim, and GKE is migrating nodes to containerd for better isolation and maintenance.
AI-written summary · about
chapters (19)
- 0:00Start
- 2:20containerd matures
- 4:34Client-Server Design
- 6:49Summary
- 8:11Pull Image
- 10:31Plugin Registration
- 11:18Recompiled with 3th party plugins
- 12:34Support Proxy
- 13:10Remote snapshotter service
- 13:49Why external runtime plugins?
- 15:25Runtime v2 API
- 17:19CRI Runtimes
- 20:08Architecture
- 20:43Performance
- 24:03Containerd in GKE
- 25:13Container Escape
- 29:26Shim V2 is Now a Standard
- 31:38GKE Sandbox Status
- 31:56Recap
related talks
29mIntroduction and Deep Dive Into Containerd
30mIntroduction and Deep Dive into containerd
21mcontainerd: Project Update and Deep Dive
29mContainerd, What Does it Mean for Me - Scott Coulton, Puppet
35mA Containerd And Friends Update: What’s New In Runtimes?
37mProject Update and Deep Dive: Containerd
37mEnhancing Node Stability Through Containerd and Kata Containers Interface...
34mContainerd: Project Update and Deep Dive