What Container Runtime Engine Do I Need?
Talkat Open Source Summit Europe 2022 · on Wednesday, 2022-09-14· at 14:20· Liffey B Part 2 (Level 1), Convention Centre Dublin, Spencer Dock, N Wall Quay, North Wall Dublin 1, D01 T1·
summary
Docker originally ships a daemon but later extracts and contributes containerd -> runc (containerd now runs under the CNCF) and Kubernetes deprecates direct Docker use via the CRI shim. Runtime choice depends on concrete needs: image build vs cluster orchestration. Rootless operation uses podman + buildah + skopeo instead of Docker; podman avoids privileged daemons. For stronger isolation choose gVisor, Firecracker or Kata; the demonstrated workflows (Docker CLI → containerd → runc, or podman/buildah pipelines) are proven and interoperable.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:51What are containers
- 4:22History of containers
- 6:32Concept of CA shoot
- 8:46Namespaces
- 10:32C Groups
- 12:42Docker
- 16:57Open Container Initiative
- 18:39Container Runtimes
- 20:00Container D
- 21:01Container C
- 22:20Container Sandbox
- 24:42Use Cases
- 26:38Build Systems
- 29:46Container Orchestration
related talks
24mOCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes
14mcontainerd: Rootless Containers 2020
34mContainer Runtimes... on Lockdown: The Hidden Costs of Multi-tenant Workloads
43mPodman, Buildah, Skopeo, and CRI-O A Year Later
39mReplacing Docker with Podman
39mMore Than Secure: Containerd + KataContainers as Kubernetes Runtime
31mYour Containers Aren’t Alone: Demystifying Container Isolation
36mExtending containerd