Kubernetes stuck in "starting..." state after 18.02.0-ce-rc1-mac50 upgrade #2536
Comments
|
There's a lot to download. Is your connection good? |
|
Yes, the connection here should be well above 200Mbps, so that shouldn't be the issue. It's still in a
|
|
yes, actually looking at your logs the problem might be elsewhere. and maybe you have something like this instead as a last line: Try removing the |
|
Current context is something work related, a different provider. Switching to the local instance I see the expected outcome: As for the complete - context:
cluster: docker-for-desktop-cluster
user: docker-for-desktop
name: docker-for-desktop
|
|
But I fear that your Docker is trying to use the wrong context. Your logs have And it's probably in the way of Docker considering that Kube is ok. What does your Kube item in the Docker menu display? |
|
Hi, Same issue for me with the last update ! Version 18.02.0-ce-rc1-mac50 (22256) |
|
Most of the time, sadly, the best is to do a factory reset. We currently have an issue with upgrading the Compose integration for Kubernetes. You can also try to take a look at the kubelet logs : |
|
That does NOT solve anything. ---- 8< ------------------------- >8 ---- |
|
I had previously allocated 2GB RAM and 2 CPU cores to the Docker Engine but needed to increase these limits today because a project needed more resources. This of course triggers a restart of Docker Engine and Kubernetes, but now nothing starts up. For reference here's the logs and it's ID I was about to do a complete reinstall of Docker when I noticed the issue but found that it didn't actually block my work; so I decided to keep it installed in case it would lead to some bug fixes. @akimd: The Kube item (context I presume?) Displays all my Now I will proceed to reinstall Docker for Mac, and hopefully the logs I've uploaded can help with discovering the upgrade issues. @MrMic: Your comment is visually easier to comprehend if you surround the logs with the three ``` |
|
Aha, I was not aware of the Anyways, once "reinstalled" Edge the naive way I still got the same issues as described above. Currently trying to do a factory reset from within the application, but it doesn't seem to be doing anything.
I tried quitting Docker mid-process since it took so long (5+ minutes without any changes) and then starting again. Nothing new happened. I decided to open up the advanced features and click Last option I see is to try and do a Now what? Well, let's install Docker Edge once again and see how it looks.
It asked for privileges, and asks me to log in with my Docker ID. That feels just about right! And look at that, Docker Engine is running! 🐳
Diagnose looks good. But it did initially as well when there were Kube issues. Let's check that commands are working properly.
Kubernetes also works! How I was able to re-install DockerGo to Docker preferences, click Reset -> Uninstall. While the bar is stuck, open Activity Monitor and force quit I wrote this as I went along, luckily it ended with a fixed issue. Not sure what went wrong along the way, but this is how I fixed my issue at least. |
|
I follow what @jarlefosen has written and finally, all is up: Docker + Kubernetes. Rgds, |
|
Hi guys, It does appear that something was wrong in the way we did the diverse "Resets", and it could spin endlessly. The next Edge will do much better in this area. I'm happy you managed to solve your issue. To bad though we could be pinpointed what it was. |
|
Thank you for following up on this issue @akimd 👏 Feel free to close this issue, but I think it's fine to have it open and visible until the next Edge release in case more people are affected by this and want to continue the conversation. |
|
I concur too. |
|
rc2 has just been released! |
|
Just upgraded it to RC2. Great to find Kubernetes v1.9.2 up and running
flawlessly.
…On 02-Feb-2018 9:43 PM, "Akim Demaille" ***@***.***> wrote:
rc2 has just been released!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2536 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AATIiHAZYmmY1ShtTbtermM5NzNeP6Wrks5tQy6cgaJpZM4RyQEV>
.
|
|
Due to China's network environment, in this case, we can refer to this solution: https://github.com/maguowei/k8s-docker-for-mac |
|
it still doesn‘t work in step 4. @Danceiny check the err log in the way: I have error message as below:
|
|
Emmmm, I think the best way should be configuring the docker proxies, I set manual proxy configuraiton, both http and https, point to 127.0.0.1:1080 (on this endpoint I opened http proxy by ssr). Actually I used both two ways（k8s-docker-for-mac and proxy） and finally I succeeded. @shidongwa |
|
thanks @Danceiny , it works for me using solution of minikube, ssr, privoxy and hyberkit. I document the steps at http://shidonghua.work/2018/05/01/mac-minikube-install/ |
|
I had installed Docker 18.05.0 CE for Mac stable then decided to install edge; so I could try Kubernetes. I uninstalled Stable then installed Edge. I was seeing the same issue Kubernetes was stuck in state "Starting". Waited for 30+ minutes no change. Solution was to uninstall; restart my Mac; then re-install Docker Edge. After this I was able to start Kubernetes and it started in a couple of mins. |
|
Yes ! I have upgraded today to the latest version of Kubernetes edge and another time |
|
I had the exact same issue, namely Kubernetes being stuck in the "Kubernetes is starting..." state after upgrading to What solved it for me was: Preferences => Reset => Reset Kubernetes cluster. However, after that I got So to summarize:
Hope this helps in other cases as well. |
|
FWIW, this is still happening (it may be indeed related to switching the
Resetting with the "nuclear option" and reinstalling seems to fix this; switching context and then back seems to "work as intended." I believe that the root cause is related to To verify this, after K8s started successfully, I switched context to another (work-related) cluster; did a Docker/Restart and observed the "Kubernetes starting..." hanging there for quite a while - switched back to the My suggestion would be to execute a check on the current context upon install/update/restart and warn the user (a "forced" context switch may be undesirable, perhaps). |
|
For me internet connection seemed to cause this issue. Not conclusive, as i reinstalled and did everything else in here before, but perhaps worth a try before trying the time consuming stuff above... |
Solution for 18.06
|
|
Same issue on Solution as above, although I actually actually did |
|
Running |
|
Still having this issue as of
|
|
Also kept having a similar looking issue (with Version 2.0.0.0-beta1-mac75 (27117)) and had to click the edit: k8s apiserver logs from before the reset (not sure that'll shed any light on what was b0rked): after which the apiserver contained exited and another was started (and this was basically crash looping forever) |
|
Hi there, Recently, I came across the same issue....Version 18.06.1-ce-mac73 (26764)...Docker version Engine: 18.06.1-ce and Kubernetes version : v1.10.3 release. Currently....both are running perfectly...
Cheers... |
|
happened today for me with Version 2.0.0.0-mac78 (28905) had to reset kubernetes |
|
👍 for a confirmation button for the reset kubernetes button, and it would also be nice if it gave some feedback that it actually did something. All I saw was Kubernetes is starting in the bottom of the dialog, then clicked the button and it still said Kubernetes is starting*, which I'd been seeing for 20 minutes already. |
|
Sorry find it.. |
|
I do Reset and all, mojave 10.14.1, and not work same at the last post |
|
I have been seeing the similar issue in version 2.0.2.1(31274) nothing working for me. |
|
Deleting the ~/.kube/config and uninstall the edge and installed the stable version fixed the issue. |
|
not working yet, the problem continue!
El mar., 9 de abr. de 2019 a la(s) 15:07, aug70.com (
notifications@github.com) escribió:
… Is this problem solved? Doesn't seem so. Why is this ticket closed?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2536 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABYl3U0f3ZQy-0DGKG86ZzniXQnzoUu_ks5vfPLjgaJpZM4RyQEV>
.
|
|
This issue persists for me... Tried all suggestions to date. |
|
Had to reset to factory defaults, since nothing else worked. This is still an issue on MAC. |
|
This issue should be re-opened. Problem continues in 19.03.2. I can't even reset to factory default since it is stuck in loading:
|
|
Happend on 2.1.0.3 (38420) stable Windows version, the same issue |
|
Same issue on 2.1.0.5 Restarting both docker and kubernetes didn't help |
|
So now what? I'm new to Docker; just spent about a week figuring out how to learn Compose and get all my stuff tweaked and perfect, decided I'd "see what the Kubernetes hoopla is all about, checked the "enable Kubernetes" option, restarted, and now I get this:
This is on the latest Edge version as of today. I just want to disable the Kubernetes option and go back to normal again, but I can't even access the settings anymore because of the spinning icon, and grayed out settings. I have tried restarting both my computer and Docker several times and it's stuck at this. I don't want to delete anything other than the Kubernetes option. I reeeeeeally don't want to destroy all my containers and images! And also don't want to destroy all of my stacks. (btw, when it says that, does it mean it will destroy ALL stacks including the ones that were there for containers created before I enabled Kubernetes? Or does it mean just the one's created after I enabled Kubernetes?) Please help! :/ |
|
@YouveGotMeowxy Have a look at this thread; it may help you to disable the Kubernetes option in the Docker GUI. It worked for me. https://geekdrop.com/content/kubernetes-in-docker-stuck-showing-kubernetes-starting-forever |
|
the problem continues in 19.03.5 |
|
I'm not a mac user, so I don't know if it is running in a VM on a mac, but on Windows I found out my vm was out of space. Expanding the space resolved this issue for me. |
If anyone facing this issue in may 2020, fixed by editing window environment variables
5.Not sure if required but i also have under no_proxy var: .company.com, localhost, |
|
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. |
and others
Expected behavior
Docker Engine and Kubernetes should start up within a reasonable time.
Actual behavior
It's been 15 minutes and Kubernetes hasn't yet started up
Docker Engine started as expected.
Information
I'm on the Edge release and I just upgraded to 18.02.0-ce-rc1-mac50 when the issue started.
Diagnose output:
Steps to reproduce the behavior
Not sure if reproducible, but these are the steps I went through.
The text was updated successfully, but these errors were encountered: