Which lightweight container runtime is designed specifically for Kubernetes and adheres to the CRI?

Which lightweight container runtime is designed specifically for Kubernetes and adheres to the CRI?

• A. CRIO
• B. containerd
• C. Docker
• D. cri-dockerd

Answer: (A)

CRI-O is a lightweight container runtime built to integrate with Kubernetes through the Container Runtime Interface. It keeps the runtime focused on running pod containers with minimal overhead, using OCI-compliant components under the hood (like runc). Because it is purpose-built for Kubernetes and implements CRI directly, it aligns tightly with how the Kubelet expects to manage containers, making it the most Kubernetes-specific and CRI-compliant choice among the options. Containerd is a solid, general-purpose runtime that can be used with Kubernetes via CRI, but it isn’t designed exclusively for Kubernetes. Docker was historically the default runtime, but Kubernetes now prefers CRI-native runtimes; Docker itself isn’t CRI-compliant without an additional shim, and cri-dockerd exists only to bridge Docker to CRI rather than serving as a Kubernetes-focused runtime.

CRI-O is a lightweight container runtime built to integrate with Kubernetes through the Container Runtime Interface. It keeps the runtime focused on running pod containers with minimal overhead, using OCI-compliant components under the hood (like runc). Because it is purpose-built for Kubernetes and implements CRI directly, it aligns tightly with how the Kubelet expects to manage containers, making it the most Kubernetes-specific and CRI-compliant choice among the options.

Containerd is a solid, general-purpose runtime that can be used with Kubernetes via CRI, but it isn’t designed exclusively for Kubernetes. Docker was historically the default runtime, but Kubernetes now prefers CRI-native runtimes; Docker itself isn’t CRI-compliant without an additional shim, and cri-dockerd exists only to bridge Docker to CRI rather than serving as a Kubernetes-focused runtime.