Troubleshooting - Docker CLI and Kubernetes Installation on Windows

Image credits - https://www.youtube.com/watch?v=Cvrqmq9A3tA

Below are some of the issues I've faced while working with Docker CLI and Kubernetes on WSL. I didn't find any straightforward solutions to it and consumed hours of Googling and troubleshooting. 

If you're facing similar issues, hope you'll find this post useful and save you the effort and time. This not only provides the final resolution but troubleshooting steps used to get to the root cause (as we learn a lot of things in the process..)

Note - This post assumes you've setup Kubernetes with kind tool. I've already covered installation of Docker CLI and Kubernetes on Windows in Part 1 and Part 2.

Issue 1: The connection to the server localhost:8080 was refused

When issuing the command 

kubectl get all

You get the following result - The connection to the server localhost:8080 was refused - did you specify the right host or port?

Troubleshooting steps:

Resolved by:

sudo /etc/init.d/docker start

You should now get all details with

kubectl get all

If no clusters found,

kind create cluster --name wslkind

Issue 2: The pod is stuck in "Pending" state for long

Troubleshooting steps:

Issue 3: The pod status is "ImagePullBackOff"

Troubleshooting steps:

As we see above, the docker image is NOT found in this node.

Note - In above, the cluster context name ideally should be "kind-wslkind" but it doesn't work. The cluster context name with which it works is "wslkind"

Now, the image can be seen

Up and running now!