-
Notifications
You must be signed in to change notification settings - Fork 286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to start kubernetes on docker desktop win 10 pro #3799
Comments
Faced the same issue today, tried this solution with no luck: #1962 (comment) |
I switched now to the EDGE channel and it looks a bit better, instead of localhost:6445 endlessly throwing the error that no nodes could be listed, the master now seems to start up, but the system pods don't start up. looking into the respective docker images, it gives the following error: |
Try deleting the PKI folder from C:\ProgramData\DockerDesktop |
Reinstalled Docker (used Edge channel, as switching before from Edge to Stable and Changing DNS configuration from Automatic to 8.8.8.8 didn't help). |
same here, using edge and deleting that folder now made both services green for me as well. thanks a lot! |
Same here, deleting the |
An initial investigation suggests this could be an installer bug when you install a new version over the top of an existing one and the certs don't get updated. Uninstalling deletes the folder so a clean uninstall / reinstall should work fine. |
Had an apparantly same issue today (Win 10 Pro, Docker Desktop - edge release) and fixed it by renaming the pki folder and resetting the Kuberenetes cluster. Thanks for the #3769 issue, guys! |
Also experienced what seems to be the same issue (Win 10 Pro, Docker Desktop Stable version 2.1.0.1 (37199), haven't tried Edge yet). As others have already mentioned, deleting the pki folder allowed the Kubernetes cluster to start, but only until the next time I rebooted at which point the symptoms reappeared. :-( |
I faced same issue even whit latest Docker Desktop version since I moved Hyper-V VM to another location. Please bellow my logs : |
as #1962 --> delete both pki & .kube folder fixed my issue |
once delete pki &.kube, reset, re-enable kubernetes, how long do you have to wait for the installation to complete? |
No need re-install, just reset |
i found a solution and the reason:
you do
|
I had same issue, today by docker updated itself.
But never starts.
my excluded port ranges are as follows:
|
i tried a |
For me this resolved it after updating latest stable version:
|
Really nice. It worked for me. Thanks. |
It worked for me also. Thanks |
This procedure also worked for me, but I had to go back and rename my .kube folder, restart the Kubernetes cluster, patiently wait several minutes or so for the lamp to turn Green again. Then: kubectl get all I haven't used kubernetes in quite a while and suspect the settings in .kube needed to be reset. |
I tried all methods in this post, it does not work. And I also tried to install it from scratch. Removed ~/AppData/{Local, roaming}/Docker*, ~/.kube, C;/programData/DockerDesktop, and reinstall it, no help. Crazy using Docker under Windows. |
I tried the solutions in this thread but Kubernetes never start. Also, while the docker client is starting, the machine cannot be reached via rdp. |
On three different Win10 I uninstalled docker desktop, deleted the folder as for this thread and reinstalled the newest stable release. |
Same here. Setup:
|
Gave up k8s in Docker for Desktop, and switched to minikube directly. |
I got the same issue and tried everything that are mentioned here but in vain. The only way that works is rolling back to version 2.1.0.5. I hope this work for you. |
Check your hosts file Maybe your antivir blocked adding entries. You need Check your logs at: I got an inifite loop message with host not found for kubernetes.docker.internal |
At least on my machine, docker desktop does not log any errors - Kubernetes just does not start. That's what makes it so hard to find the error in the first place... ;) |
Don't know why this is happening but actually works. Thanks! |
Not for me. The diagnostic log of Docker destkop is definitely insufficient and the whole experience (in case of problems) very bad. |
Kubernetes can take time to start if you don't have a good machine took around 1-3 minutes |
After updating to docker desktop v2.3.0.4 from prev version on windows 10 pro 64bit, i too faced the issue. After enabling kubernetes, it appeared stuck on starting. But it was not stuck and it came back after a considerable delay. It worked for me even though i am behind corporate proxy and using cisco anyconnect vpn too. Keep on watching the following log files to known the progress. For me it took lot of time for kubernetes to come up. |
As @aaraodeo suggested, look at log files for issues. For me it was to do with insufficient accessibility to certain folders which I found via %USERPROFILE%\AppData\Local\Docker\log.txt It is working again now. |
Issues go stale after 90 days of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Docker desktop Version 3.0.0 (50684), Kubernetes 1.19.3 |
The logs show very stupid actions:
The folder should be instead |
In the setting touch reset kubernetes cluster and restart docker. Enable kubernetes and wait, don 't select the other options. |
@bielolopez I did several times and it does NOT work. The bad bug is how docker client is building the path, forgetting the backslash between the user home folder and the .kube relative folder. |
Then you will have to uninstall docker and delete .kube and .docker in the / user / raffaeler / document folder and docker and docker desktop in ProgramData, as well as in I think it should work. |
Thank you @bielolopez but I will stay with my fake folder for the moment in order to avoid losing the current containers BTW I don't see how a path concatenation could be resolved by deleting all those folders.
I am very worried about the low consideration that Docker has for the users who encountered this issue that is open since April 23, 2019. |
You're welcome raffaeler, look at this to see if you can solve it, I know that at the beginning I had a problem with kubernetes and I did not raise them with w2l but with hyper-v. Look at this link: |
Thank you @bielolopez |
I upgraded docker desktop version to the latest today (12/21/2020). Docker started but the kubernetes is showing its starting but its not. The logs are as below. Have tried almost all the solution in the thread but none seem to solve this issue Version: 3.0.0 (50684) File: C:\Users\shsslk-adm\AppData\Local\Docker\log.txt |
From what I see in the log, it is an image that is downloaded that the DNS does not have certificates or is not configured. What it would do would be to remember if before closing docker which image you used or did you pull or docker-compose, etc. To delete it and restart docker and the whole team. |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Expected behavior
Run Kubernetes on windows docker
Actual behavior
Kubernetes doesnt start up.
Information
Steps to reproduce the behavior
It looks like the proxy / network is somehow not working correctly, but all configs that I know of are to my knowledge correctly configured.
If anyone has any idea, I would be very grateful, I am now out of ideas and solutions how to get Kubernetes up and running locally.
The text was updated successfully, but these errors were encountered: