DevOps · Flashcard
What replaced dockershim after its removal in Kubernetes 1.24?
- ACRI-native runtimes like containerd and CRI-O — the kubelet talks to them over the CRI directly
- BA rewritten dockershim maintained by Kubernetes — kept in-tree under a new component name
- CDocker Engine speaking CRI natively — updated so the kubelet can call it without any adapter
- DA cloud-provider shim bundled with each distro — vendor code translating Docker calls to CRI
Why this is the answer
With dockershim gone, nodes use CRI-native runtimes such as containerd or CRI-O directly. Kubernetes did not keep a renamed in-tree shim, Docker Engine itself did not gain native CRI, and the fix was not per-vendor shims — the CRI runtimes already existed.
Official docs