Skip to content

container-runtime.md

Latest commit

 

History

History
62 lines (43 loc) · 1.88 KB

container-runtime.md

File metadata and controls

62 lines (43 loc) · 1.88 KB

🐳 Container Runtime – The Engine Room of Kubernetes

🔹 What is a Container Runtime?

A container runtime is the low-level software responsible for:

  • Pulling container images
  • Creating and running containers
  • Isolating them using Linux namespaces & cgroups

It’s the component that actually executes the containerized apps described in your Pods.

🔹 Role in Kubernetes

Kubernetes does NOT run containers directly. Instead:

  • The kubelet talks to the container runtime
  • The runtime does the real work of starting, stopping, and monitoring containers

This communication happens through a standardized interface: CRI (Container Runtime Interface).

🔗 Integration with Kubernetes – CRI

📦 What is CRI?

The Container Runtime Interface (CRI) is a gRPC API used by kubelet to communicate with any container runtime.

Without CRI With CRI
Tight coupling Loose, pluggable design
Only Docker support Support for many runtimes
Hard to extend Easy to swap runtimes

🔧 Popular Kubernetes-Compatible Runtimes

Runtime Description
containerd Lightweight, production-grade runtime used by most distros (including Docker under the hood)
CRI-O Kubernetes-native, minimal runtime for OpenShift and RHEL
Docker Legacy runtime (deprecated since K8s v1.20)
gVisor Sandbox runtime focused on security
Kata Containers Lightweight VMs instead of containers (for isolation)
Mirantis Container Runtime Enterprise Docker continuation

🔁 How the Flow Works

[kube-apiserver]
       ↓
     kubelet
       ↓ (CRI gRPC)
[container runtime]
       ↓
  Pull image, run container