Explore the Kubernetes view

Docker Desktop includes a standalone Kubernetes server and client, as well as Docker CLI integration, enabling local Kubernetes development and testing directly on your machine.

The Kubernetes server runs as a single or multi-node cluster, within Docker containers. This lightweight setup helps you explore Kubernetes features, test workloads, and work with container orchestration in parallel with other Docker features.

Enable Kubernetes

With Docker Desktop version 4.51 and later, you can manage Kubernetes directly from the Kubernetes view in the Docker Desktop Dashboard.

1. Open the Docker Desktop Dashboard and select the Kubernetes view.
2. Select Create cluster.
3. Choose your cluster type:
   • Kubeadm creates a single-node cluster and the version is set by Docker Desktop.
   • kind creates a multi-node cluster and you can set the version and number of nodes. For more detailed information on each cluster type, see Cluster provisioining method.
4. Optional: Select Show system containers (advanced) to view internal containers when using Docker commands.
5. Select Create.

This sets up the images required to run the Kubernetes server as containers, and installs the kubectl command-line tool on your system at /usr/local/bin/kubectl (Mac) or C:\Program Files\Docker\Docker\resources\bin\kubectl.exe (Windows). If you installed kubectl using Homebrew, or by some other method, and experience conflicts, remove /usr/local/bin/kubectl.

Note

Docker Desktop for Linux does not include kubectl by default. You can install it separately by following the Kubernetes installation guide. Ensure the kubectl binary is installed at /usr/local/bin/kubectl.

The following actions are also triggered in the Docker Desktop backend and VM:

• Generation of certificates and cluster configuration
• Download and installation of Kubernetes internal components
• Cluster bootup
• Installation of additional controllers for networking and storage

When Kubernetes is enabled, its status is displayed in the Docker Desktop Dashboard footer and the Docker menu.

You can check which version of Kubernetes you're on with:

$ kubectl version

Cluster provisioning method

Docker Desktop Kubernetes can be provisioned with either the kubeadm or kind provisioners.

kubeadm is the older provisioner. It supports a single-node cluster, you can't select the kubernetes version, it's slower to provision than kind, and it's not supported by Enhanced Container Isolation (ECI), meaning that if ECI is enabled the cluster works but it's not protected by ECI.

kind is the newer provisioner. It supports multi-node clusters (for a more realistic Kubernetes setup), you can choose the Kubernetes version, it's faster to provision than kubeadm, and it's supported by ECI - when ECI is enabled, the Kubernetes cluster runs in unprivileged Docker containers, thus making it more secure.

Dashboard view

When a Kubernetes cluster is enabled, the Kubernetes view displays a live dashboard view showing:

• A namespace selector at the top
• A real-time list of resources - pods, services, deployments - in the selected namespace
• Automatic updates when resources are created, deleted, or modified

Verify installation

Confirm that your cluster is running:

$ kubectl get nodes
NAME                 STATUS    ROLES            AGE       VERSION
docker-desktop       Ready     control-plane    3h        v1.29.1

If kubectl is pointing to another environment, switch to the Docker Desktop context:

$ kubectl config use-context docker-desktop

Tip

If no contexts appear, try:

• Running the command in the Command Prompt or PowerShell.
• Setting the KUBECONFIG environment variable to point to your .kube/config file.

For more information about kubectl, see the kubectl documentation.

Edit or stop your cluster

When Kubernetes is enabled:

• Select Edit cluster to modify configuration. For example, switch between kubeadm and kind, or change the number of nodes.
• Select Stop to disable the cluster. Progress is displayed, and the Kubernetes view returns to the Create cluster screen. This stops and removes Kubernetes containers, and also removes the /usr/local/bin/kubectl command.

Upgrade your cluster

Kubernetes clusters are not automatically upgraded with Docker Desktop updates. To upgrade the cluster, you must manually select Reset cluster in the Kubernetes settings.

Configuring a custom image registry for Kubernetes control plane images

Docker Desktop uses containers to run the Kubernetes control plane. By default, Docker Desktop pulls the associated container images from Docker Hub. The images pulled depend on the cluster provisioning mode.

For example, in kind mode it requires the following images:

docker.io/kindest/node:<tag>
docker.io/envoyproxy/envoy:<tag>
docker.io/docker/desktop-cloud-provider-kind:<tag>
docker.io/docker/desktop-containerd-registry-mirror:<tag>

In kubeadm mode it requires the following images:

docker.io/registry.k8s.io/kube-controller-manager:<tag>
docker.io/registry.k8s.io/kube-apiserver:<tag>
docker.io/registry.k8s.io/kube-scheduler:<tag>
docker.io/registry.k8s.io/kube-proxy
docker.io/registry.k8s.io/etcd:<tag>
docker.io/registry.k8s.io/pause:<tag>
docker.io/registry.k8s.io/coredns/coredns:<tag>
docker.io/docker/desktop-storage-provisioner:<tag>
docker.io/docker/desktop-vpnkit-controller:<tag>
docker.io/docker/desktop-kubernetes:<tag>

The image tags are automatically selected by Docker Desktop based on several factors, including the version of Kubernetes being used. The tags vary for each image and may change between Docker Desktop releases. To stay informed, monitor the Docker Desktop release notes.

To accommodate scenarios where access to Docker Hub is not allowed, admins can configure Docker Desktop to pull the above listed images from a different registry (e.g., a mirror) using the KubernetesImagesRepository setting as follows.

An image name can be broken into [registry[:port]/][namespace/]repository[:tag] components. The KubernetesImagesRepository setting allows users to override the [registry[:port]/][namespace] portion of the image's name.

For example, if Docker Desktop Kubernetes is configured in kind mode and KubernetesImagesRepository is set to my-registry:5000/kind-images, then Docker Desktop will pull the images from:

my-registry:5000/kind-images/node:<tag>
my-registry:5000/kind-images/envoy:<tag>
my-registry:5000/kind-images/desktop-cloud-provider-kind:<tag>
my-registry:5000/kind-images/desktop-containerd-registry-mirror:<tag>

These images should be cloned/mirrored from their respective images in Docker Hub. The tags must also match what Docker Desktop expects.

The recommended approach to set this up is the following:

1. Start Kubernetes using the desired cluster provisioning method: kubeadm or kind.
2. Once Kubernetes has started, use docker ps to view the container images used by Docker Desktop for the Kubernetes control plane.
3. Clone or mirror those images (with matching tags) to your custom registry.
4. Stop the Kubernetes cluster.
5. Configure the KubernetesImagesRepository setting to point to your custom registry.
6. Restart Docker Desktop.
7. Verify that the Kubernetes cluster is using the custom registry images using the docker ps command.

Note

The KubernetesImagesRepository setting only applies to control plane images used by Docker Desktop to set up the Kubernetes cluster. It has no effect on other Kubernetes pods.

Note

In Docker Desktop versions 4.43 or earlier, when using KubernetesImagesRepository and Enhanced Container Isolation (ECI) is enabled, add the following images to the ECI Docker socket mount image list:

[imagesRepository]/desktop-cloud-provider-kind: [imagesRepository]/desktop-containerd-registry-mirror:

These containers mount the Docker socket, so you must add the images to the ECI images list. If not, ECI will block the mount and Kubernetes won't start.

Troubleshooting

• If Kubernetes fails to start, make sure Docker Desktop is running with enough allocated resources. Check Settings > Resources.
• If the kubectl commands return errors, confirm the context is set to docker-desktop

  $ kubectl config use-context docker-desktop
  

  You can then try checking the logs of the Kubernetes system containers if you have enabled that setting.
• If you're experiencing cluster issues after updating, reset your Kubernetes cluster. Resetting a Kubernetes cluster can help resolve issues by essentially reverting the cluster to a clean state, and clearing out misconfigurations, corrupted data, or stuck resources that may be causing problems. If the issue still persists, you may need to clean and purge data, and then restart Docker Desktop.