1 views collected around this technical thread.
This article introduces four leading open‑source container platforms—Docker, Podman, Containerd, and CRI‑O—detailing their core features, architecture, and use‑case advantages, helping readers understand each product’s strengths and suitability for modern cloud‑native and micro‑service deployments.
This article introduces several widely used container engines—including Docker, Podman, LXD, Containerd, and CRI‑O—explaining their core components, architectural differences, security features, and typical use cases for developers and operations teams.
After Kubernetes announced the deprecation of Docker in version 1.24, this article examines several Docker alternatives—containerd, Podman, LXC/LXD, rkt, OpenVZ, Singularity, and CRI‑O—detailing their core features and advantages over Docker for modern cloud‑native environments.
This guide explains why Kubernetes dropped dockershim, clarifies OCI and CRI standards, compares Docker, containerd and cri‑o runtimes, and provides a step‑by‑step procedure—including node draining, Docker removal, kernel tuning, cri‑o installation, kubelet reconfiguration, and verification—to successfully migrate a cluster from Docker to cri‑o before upgrading to version 1.24.
This article explains the key components and standards of the container ecosystem—including Docker, containerd, CRI‑O, OCI and runc—detailing how they interact, the role of the Container Runtime Interface, and why Docker is only a small part of a broader, interoperable cloud‑native landscape.
Kubernetes has officially deprecated Docker support by removing the dockershim bridge, explaining that Docker lacks native CRI compliance, and recommends migrating to CRI‑compatible runtimes such as containerd or CRI‑O while clarifying the differences between CRI and OCI runtimes.
Kubernetes has removed Docker support by deprecating the dockershim bridge, urging users to adopt CRI‑compatible runtimes such as containerd or CRI‑O, and explaining the differences between CRI and OCI runtimes, their security implications, and migration recommendations.
Starting with version 1.20 Kubernetes deprecates Docker as a container runtime, but Docker images remain usable through CRI‑compatible runtimes like containerd or CRI‑O, so developers can keep building with Docker while clusters transition to supported runtimes with minimal disruption.
This article examines how Mirantis’ acquisition of Docker, the historical contributions of major vendors, and the development of container runtimes such as LXC, runc, CRI‑O, and containerd have shaped the modern cloud‑native ecosystem and OpenShift’s architecture.