Container Engines and Runtimes logopeterindia.net
Knowledge Hub

Container Engines and Runtimes

Container engines and runtimes: containerd, CRI-O, Podman, runc, crun, gVisor, Kata Containers, Firecracker and WebAssembly runtimes.

20 topics•5 categories•Updated November 18, 2026

What Are Container Engines and Runtimes?

4 entries

A container runtime starts and manages containers. High-level runtimes such as containerd, CRI-O and Podman pull images and manage container lifecycles, while low-level OCI runtimes such as runc, crun and youki create the container process. Sandboxed runtimes such as gVisor, Kata Containers and Firecracker add stronger isolation. Descriptions below follow each project's own pages; release facts come from GitHub.

High-Level Container Engines and Runtimes

6 entries

Engines that manage images and container lifecycles and are used directly or by Kubernetes.

Low-Level OCI Runtimes

3 entries

Runtimes that create containers according to the Open Container Initiative runtime specification.

Sandboxed and Confidential Runtimes

3 entries

Runtimes that add isolation between containers and the host.

WebAssembly and HPC Runtimes

2 entries

Runtimes for other workload types.

Standards and References

2 entries

Specifications and documentation for container runtimes.

Frequently Asked Questions

What is a container runtime?

Software that starts and manages containers. High-level runtimes such as containerd, CRI-O and Podman handle images and lifecycles, and they call low-level OCI runtimes such as runc or crun to create the container process.

What is the difference between containerd, CRI-O and Docker?

containerd and CRI-O are container runtimes that Kubernetes can use through the Container Runtime Interface. Docker Engine is a fuller developer tool built on containerd and runc. Kubernetes removed Dockershim in release 1.24, so clusters use a CRI runtime directly.

What are OCI runtimes?

Runtimes that follow the Open Container Initiative runtime specification to create containers, such as runc, crun and youki. They are usually invoked by containerd, CRI-O or Podman rather than used directly.

When do I need a sandboxed runtime such as gVisor or Kata Containers?

When containers from different tenants or untrusted code share a host. gVisor interposes an application kernel and Kata Containers runs each pod in a lightweight virtual machine, both adding isolation beyond standard Linux namespaces at some performance cost.

Can containers run WebAssembly?

Runtimes such as WasmEdge run WebAssembly workloads and can integrate with container tooling, as an alternative to Linux containers for some edge and serverless use cases.