Skip to content
BENIBIX Learn

Container Runtime

Infrastructure📦 ContainersRuntimes and Tools

Also known as containerd, CRI-O, runc

The program under the hood that starts and stops containers. Other tools hand it the work.

Think of it like

It is like the engine in a car. You turn the key, and the engine does the real work.

Example

Kubernetes dropped its built-in link to Docker in version 1.24. Clusters moved to containerd or CRI-O. The same images kept working.

Why it matters

Because images follow one standard, you are not locked to one tool. You can change the runtime and keep your images.

Definition

A container runtime is the program that really starts and stops containers. It builds the walls around each one, so it sees only its own files. Tools you type into, like Docker or Podman, hand the job down to it. Common runtimes are containerd, CRI-O and runc. Images follow an open standard, so any runtime that follows it can run them.
The runtime sits on the shared kernel. It is what turns each image into a running container.

Common mistake

Thinking Docker is the only way to run a container. Docker is one tool on top of a runtime, and others work too.

Key takeaways

  1. 1
    Does the real work. It starts, stops and watches containers.
  2. 2
    Builds the walls. Each container gets its own space.
  3. 3
    Follows the standard. Any standard image runs on it.