Docker for Desktop Kubernetes Unable to connect to the server: dial tcp [::1]:6445 Docker for Desktop Kubernetes Unable to connect to the server: dial tcp [::1]:6445 kubernetes kubernetes

Docker for Desktop Kubernetes Unable to connect to the server: dial tcp [::1]:6445


I know this is an old question but the following helped me to resolve a similar issue. The root cause was that I had minikube installed previously and that was being used as my default context.I was getting following error:

Unable to connect to the server: dial tcp 192.168.1.8:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

In the power-shell run the following command:

> kubectl config get-contextsCURRENT   NAME                 CLUSTER          AUTHINFO         NAMESPACE      docker-desktop       docker-desktop   docker-desktop      docker-for-desktop   docker-desktop   docker-desktop*     minikube             minikube         minikube

this will list all the contexts and see if there are multiple. If you had installed minikube in the past, that will show a * mark as currently selected default context. You can change that to point to docker-desktop context like follows:

> kubectl config use-context docker-desktop

Run the get-contexts command again to verify the * mark.

Now, the following command should work:

> kubectl get pods


Posting a response to this very old question, as I was searching for a solution and later found a different cause for my problem and the solution was simple.

  1. Cause was that the config file was missing from the $HOME$/.kube directory

  2. A simple restart of Docker Desktop restored the file with some defaults and things were back ok.

Side note: The issue started after I upgraded my Docker Desktop Installation to latest (when I got the update available popup). I should also mention that the cluster stopped working and I had to manually remove Docker Desktop and Reinstall the latest version (this was the story before the problem occurred).