CRI-O
A lightweight open-source container runtime designed specifically for Kubernetes that natively implements the CRI and OCI specifications.
Timeline (last 90 days)
It took containerd and CRI-O several years each to become the default choice for container runtimes.
Both containerd and CRI-O natively implement CRI.
Runtimes such as containerd, CRI-O, and Podman all implement the OCI runtime specification.
Container runtimes (such as containerd and CRI-O) pull images, create namespaces, and mount filesystems so that processes inside the container believe they have a machine to themselves.
runc is the reference implementation of the OCI Runtime Spec, and containerd and CRI-O wrap image management and lifecycle management capabilities on top of it.
containerd was originally split out from the Docker architecture, is currently hosted by CNCF and has graduated; CRI-O is led by Red Hat and does not support Docker-exclusive APIs.
现代容器运行时分为高级运行时(如containerd、CRI-O)和低级运行时(如runc)两层
容器运行时通常分为高级运行时(如containerd、CRI-O)和低级运行时(如runc)两层,低级运行时直接调用Linux内核的namespace和cgroup机制实现进程隔离和资源限制
Docker 镜像遵循 OCI 标准,任何兼容 OCI 的运行时(如 containerd、CRI-O)都可以运行 Docker 构建的镜像
All Facts (9)
It took containerd and CRI-O several years each to become the default choice for container runtimes.
50%UnverifiedBoth containerd and CRI-O natively implement CRI.
50%UnverifiedRuntimes such as containerd, CRI-O, and Podman all implement the OCI runtime specification.
50%UnverifiedContainer runtimes (such as containerd and CRI-O) pull images, create namespaces, and mount filesystems so that processes inside the container believe they have a machine to themselves.
50%Unverifiedrunc is the reference implementation of the OCI Runtime Spec, and containerd and CRI-O wrap image management and lifecycle management capabilities on top of it.
50%Unverifiedcontainerd was originally split out from the Docker architecture, is currently hosted by CNCF and has graduated; CRI-O is led by Red Hat and does not support Docker-exclusive APIs.
50%Unverified现代容器运行时分为高级运行时(如containerd、CRI-O)和低级运行时(如runc)两层
50%Unverified容器运行时通常分为高级运行时(如containerd、CRI-O)和低级运行时(如runc)两层,低级运行时直接调用Linux内核的namespace和cgroup机制实现进程隔离和资源限制
50%UnverifiedDocker 镜像遵循 OCI 标准,任何兼容 OCI 的运行时(如 containerd、CRI-O)都可以运行 Docker 构建的镜像
50%