Repository files navigation

This adapter provides a shim forDocker Enginethat lets you control Docker via theKubernetesContainer Runtime Interface.

Take a look at theofficial docs for more information.

For users running0.2.5 or above, the default network plugin iscni. Kubernetes 1.24+ has removedkubenet andother network plumbing from upstream as part of thedockershim removal/deprecation. In order for a cluster to becomeoperational, Calico, Flannel, Weave, or another CNI should be used.

For CI workflows, basic functionality can be provided viacontainernetworking/plugins.

Mirantis and Docker have agreed to partner to maintain the shim code standalone outside Kubernetes, as a conformant CRIinterface for the Docker Engine API. For Mirantis customers, that means that Docker Engine’s commercially supportedversion, Mirantis Container Runtime (MCR), will be CRI compliant. This means that you can continue to build Kubernetesbased on the Docker Engine as before, just switching from the built in dockershim to the external one.

Mirantis and Docker intend to work together on making sure it continues to work as well as before and that itpasses all the conformance tests and continues to work just like the built in version did. Mirantis will be usingthis in Mirantis Kubernetes Engine, and Docker will continue to ship this shim in Docker Desktop.

You can find more information about the context for thistool inDon't Panic: Kubernetes and Dockerand on the Mirantisblog.

We can be found on theKubernetes Slack in the#cri-dockerd channel.

Refer to theinstall page for instructions on how to installcri-dockerd using a package manager.

If you want to runcri-dockerd on an unsupported platform, instructions can be found on themanual install page.

If you want to usecri-dockerd with Kubernetes, you can find instructions on theKubernetes page.

We welcome contributions tocri-dockerd. If you would like to contribute, please refer to the development section of theofficial docs.

The docs are generated usingHugo and theGeekdocs theme. Hugo will need to be installed to generate the docs found in thedocs/ directory.

The docs can be ran locally with hot-reloading to make editing easier. To do so, run the following command in the project's root directory:

make docs

This will launch the development server that is included with Hugo. You can then access the docs athttp://localhost:1313/