Stuck with kubernetes failed to start in docker desktop error? We can help you.

As part of our Server Management Services, we assist our customers with several Kubernetes queries.

Today, let us see how our Support techs proceed to resolve it.

How to resolve kubernetes failed to start in docker desktop?

Typical error looks as shown below:

Unable to connect to the server: dial tcp 127.0.0.1:6443: connectex: No
connection could be made because the target machine actively refused it.

Today, let us see the steps followed by our Support Techs to resolve it.

1. Select the items marked with the red color in Troubleshoot

1. Firstly, reset Kubernetes cluster
2. Then, clean/Purge data
3. Next, reset to factory setting
4. Finally, uninstall Docker for Mac

2. Remove Docker for Mac from Applications

There are two ways. One is to remove Docker for Mac from Applications, and another is to replace the Docker for Mac with the new installation listed in the step 3.

3. Re-install Docker for Mac

1. Firstly, click Docker.dmg

2. Then, drag and drop Docker for Mac to Applications

If the old Docker has not manually removed from Applications. Mac usually reminds a user to replace the old one with a new installed Docker for Mac.

3. Then, open and Verify Docker for Mac

4. Finally, remove both pki and kube

$ rm -rf ~/Library/Group\ Containers/group.com.docker/pki/
$ rm -rf ~/.kube

5. Set the items in Preferences

1.General

Do not set tick for Start Docker Desktop when you log in. It wastes a lot of time while dealing with the Troubleshoot.

2.Resources –> Advanced –> Swap

It is preferable to set Swap to 0 GB (or zero GB) because Kubernetes sometimes
keep starting while the Swap is set to any number being larger than 0 GB.

Kubernetes is designed to use up the DRAM resource according to the Google principle.

Swap is regarded as a bad habit in Kubernetes.

$ sudo swapoff -a
(for Nvidia portable machines)

3. Kubernetes

Select the tick to Enable Kubernetes

4. Apply & Restart

It usually take from 6 to 15 minutes to complete the setting depending on the factors including network speed, vpn and machine capabilities.

It still has the unforeseeable factors to stop the successful configuration of Kubernetes even though adopting the above-strict steps.

Or it functions bad for re-starting sometimes.

[Stuck in between? We’d be glad to assist you]

Conclusion

In short, today we saw steps followed by our Support Techs resolve Kubernetes failed to start in docker desktop error.