Container Runtimes
Docker / Container Runtime Content
- Scope: Everything container-runtime related -
containerd,ctr,nerdctlandcrictl. - No Kubernetes required: These labs work directly against the container runtime. A kind worker node is used only as a disposable containerd host - you interact with it through plain
docker exec, never withkubectl.
What you’ll learn
- How Docker, containerd, CRI and the CLIs (
ctr,nerdctl,crictl) relate to each other - Managing images, containers, namespaces, content and snapshots directly through containerd
- Debugging containers from the exact interface orchestrators use (CRI)
- Using
nerdctlas a drop-in Docker replacement (build, run, compose, debug)
🧩 How the tools fit together
┌──────────────────────────────────────────────────────────┐
│ docker CLI ──► dockerd ──► containerd ──► runc │
│ │
│ nerdctl CLI ────────────────► containerd ──► runc │
│ │
│ crictl CLI ──► CRI (container runtime API) ──► runc │
└──────────────────────────────────────────────────────────┘
| Tool | Talks to | Think of it as… |
|---|---|---|
| docker | dockerd (high-level daemon) | The familiar developer CLI |
| ctr | containerd (native) | Low-level, scriptable containerd client |
| nerdctl | containerd (direct) | Docker-compatible CLI without dockerd |
| crictl | CRI (container runtime API) | The CLI that node agents use under the hood |
🗂️ Labs in this section
| # | Lab | Description |
|---|---|---|
| 19 | Containerd CLI (ctr) | Manage images, containers, namespaces, content and snapshots via containerd |
| 20 | CRI Debugging (crictl) | Inspect and troubleshoot containers and images at the CRI level |
| 21 | Nerdctl (nerdctl) | Build, run, compose and debug containers with a drop-in Docker replacement |
🚀 Running the course stack with Docker only
The course apps (nginx, app1, app2, buggy) run with nothing but Docker Compose:
Full port map, URLs and cleanup: 🐳 Run with Docker Only