Container Runtime Basics
You'll learn: What container runtimes are and how they make containers actually run on your system.
What Is a Container Runtime?
A container runtime is the low-level software that executes and manages containers on a host machine. While container images define what should run, the runtime is the engine that actually brings those images to life as running processes.
Think of it like this: if a container image is a movie file, the container runtime is your media player. You need both the content and the player to watch anything.
Common Container Runtimes
Docker Engine is the most familiar runtime. It's a complete platform that includes both high-level commands (docker run, docker build) and the underlying execution engine. When you interact with Docker, you're usually working through Docker Engine.
containerd (pronounced "container-dee") is a lower-level runtime that Docker Engine itself uses under the hood. It handles the core container lifecycle: pulling images, managing storage, and executing containers. Many Kubernetes clusters use containerd directly, skipping Docker's extra layers.
CRI-O is specifically designed for Kubernetes. It implements the Container Runtime Interface (CRI) specification and focuses on being lightweight and purpose-built for orchestration environments.
How They Differ
Docker Engine provides a complete developer experience with many tools bundled together. containerd and CRI-O are more focused and minimal—they do container execution efficiently without extra features. You'd typically interact with containerd or CRI-O through an orchestrator like Kubernetes rather than directly.
Key Takeaway: Container runtimes are the engines that execute containers from images—Docker Engine offers a full platform, while containerd and CRI-O provide focused, lower-level execution for orchestrated environments.