Dockershim deprecation does NOT impact kind.  🐳

If you already use kind you've actually been testing your workloads on containerd!

While kind uses docker or podman on your host, it uses CRI / containerd "inside" the nodes and does not use dockershim.

Carry on and be KiND! ❤️

Local Registry

This guide covers how to configure KIND with a local container image registry.

In the future this will be replaced by a built-in feature, and this guide will cover usage instead.

Create A Cluster And Registry 🔗︎

The following shell script will create a local docker registry and a kind cluster with it enabled.

set -o errexit

# create registry container unless it already exists
if [ "$(docker inspect -f '{{.State.Running}}' "${reg_name}" 2>/dev/null || true)" != 'true' ]; then
  docker run \
    -d --restart=always -p "${reg_port}:5000" --name "${reg_name}" \

# create a cluster with the local registry enabled in containerd
cat <<EOF | kind create cluster --config=-
kind: Cluster
- |-
    endpoint = ["http://${reg_name}:5000"]

# connect the registry to the cluster network if not already connected
if [ "$(docker inspect -f='{{json .NetworkSettings.Networks.kind}}' "${reg_name}")" = 'null' ]; then
  docker network connect "kind" "${reg_name}"

# Document the local registry
cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: ConfigMap
  name: local-registry-hosting
  namespace: kube-public
  localRegistryHosting.v1: |
    host: "localhost:${reg_port}"
    help: ""

Using The Registry 🔗︎

The registry can be used like this.

  1. First we'll pull an image docker pull
  2. Then we'll tag the image to use the local registry docker tag localhost:5000/hello-app:1.0
  3. Then we'll push it to the registry docker push localhost:5000/hello-app:1.0
  4. And now we can use the image kubectl create deployment hello-server --image=localhost:5000/hello-app:1.0

If you build your own image and tag it like localhost:5000/image:foo and then use it in kubernetes as localhost:5000/image:foo.