study.

containerd learning path

Distinguish images, containers, and tasks using ctr, nerdctl, and crictl.

Six labs target rootful containerd on Linux. Installation, upgrades, and production node configuration changes are outside scope. The CRI lab requires a Kubernetes node.

Use a personal Linux practice VM with containerd, runc, ctr, and sudo access. The nerdctl lab also needs nerdctl; the CRI lab needs crictl and a practice node with CRI enabled. Examples assume /run/containerd/containerd.sock; check the actual socket in other environments.

Learn with progress and quizzes

Essential concepts before you start

OCI, CRI, and containerd

OCI defines image and runtime specifications; CRI is the interface between kubelet and a container runtime. containerd is a runtime service and can use an OCI runtime such as runc. Distinguish standards, interfaces, and executable implementations.

Images, Containers, and Tasks

An image supplies execution content, a Container holds metadata such as image and command, and a Task represents execution. A newly created Container can legitimately have no Task. Observe process termination separately from metadata deletion.

Namespaces and sockets

The socket identifies a daemon and the namespace scopes its metadata. Changing either can change command results. A containerd namespace is neither a Kubernetes namespace nor a security boundary against administrative access.

Content storage and snapshots

Content storage manages data such as manifests and blobs; snapshotters prepare filesystem state for execution. Removing one image reference need not remove data shared by other objects. Inspect references and supported cleanup rather than deleting internal files.

Choosing ctr, nerdctl, or crictl

ctr supports low-level containerd inspection, nerdctl provides Docker-like workflows, and crictl observes CRI sandboxes and containers. Align API, namespace, and rootless or rootful context when comparing results on the same host.

Image pulls, execution, and networking

A successful pull does not prove process startup or networking works. Execution depends on runtime and host capabilities; networking may require additional plugins. Identify the failed stage instead of repeatedly downloading the image.

Architecture & Images

Understand daemon/client roles and namespaced images.

Container Execution

Observe task lifetimes and nerdctl execution.

CRI & Diagnostics

Separate CRI observations from host runtime health.