Mirantis/cri-dockerd

Health v2 · maintenance only

Adoption not part of the score

1362 stars · 352 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

cri-dockerd is an adapter that exposes the Docker Engine as a Kubernetes-compliant Container Runtime Interface (CRI), replacing the removed built-in dockershim. It is maintained by Mirantis and Docker so Kubernetes clusters can keep using Docker Engine as their container runtime.

Use cases

• run kubernetes with docker engine after dockershim removal
• upgrade kubernetes cluster to 1.24+ while keeping docker runtime
• make docker engine cri compliant
• configure kubelet to use docker as container runtime
• use docker desktop as kubernetes container runtime

When to choose

• you rely on Docker Engine tooling or Mirantis Container Runtime and need a Kubernetes-conformant runtime
• you are migrating clusters off the removed in-tree dockershim
• you use Docker Desktop's Kubernetes integration

When to avoid

• you are starting a new cluster with no Docker dependency - containerd or CRI-O are simpler and more direct
• you need the highest performance runtime without an extra shim layer
• you require kubenet networking, which was removed alongside dockershim

Facets

service · maturity active

container-runtime developer-tools cloud-computing windows go cri dockershim docker-engine kubernetes-runtime shim-adapter containers devops linux docker kubernetes

Member repositories

For agents

markdown · JSON · MCP: product_card(name="Mirantis/cri-dockerd")