4 ms·
Kubernetes used to (tediously) pass everything through to Docker, but since 1.20, that's resolved, and it now uses containerd.
by richardwhiuk 5y ago
Kubernetes used to (tediously) pass everything through to Docker, but since 1.20, that's resolved, and it now uses containerd.
- p_l 5y agoNot everything - for a bunch of things, the actual setup increasingly happened outside docker then docker was just informed how to access it, bypassing all the higher level logic in Docker. 1.20 is when docker mode got deprecated, IIRC, but many of us were already happily running in containerd for some time.
- qwertywert_ 5y agoI thought its moving to CRI-o as well instead of containerd, or is k8s just not using docker, and containerd still supported in the future?
- p_l 5y agoCRI-O is the target and containerd is the most common runtime implementing it at the moment.
- qwertywert_ 5y agoAre you sure? This isn't my subject area but CRI-O looks like an alternative to containerd and implements the OCI compliant runtime like containerd does. And then there is a 3rd which is docker engine which is the one being dropped.
- p_l 5y agoSorry, I mixed up CRI and CRI-O. The roadmap is to remove dockershim (the interface to docker-compatible container runtime) and use only CRI - of which containerd and CRI-O are two compatible implementations.