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: Docker for Mac: version: 18.02.0-ce-rc1-mac50 (e1912a8c46ae6f60a85d277f7b8d210dc9670b28) macOS: version 10.12.6 (build: 16G1114) logs: /tmp/5F73B1D4-3EBF-408F-95D6-E28BDE7A7CEF/20129.tar.gz [OK] db.git [OK] vmnetd [OK] dns [OK] driver.amd64-linux [OK] virtualization VT-X [OK] app [OK] moby [OK] system [OK] moby-syslog [OK] kubernetes [OK] env [OK] virtualization kern.hv_support [OK] slirp [OK] osxfs [OK] moby-console [OK] logs [OK] docker-cli [OK] menubar [OK] disk Steps to reproduce the behavior Not sure if reproducible, but these are the steps I went through. • Early January switch from Stable to Edge releases of Docker to get 17.12 (if I remember correctly) • Enable Kubernetes •. Wait until today • Upgrade Docker to 18.02. That does NOT solve anything. I have removed completely Docker and reinstall it.

Fast and Easy Setup. Kitematic's one click install gets Docker running on your Mac and lets you control your app containers from a graphical user interface (GUI).

Kubernetes still do NOT start! The kubelet.err.log is: --- 88 ---- And now?? You release something that you even try on a Mac OSX? Seriously, you will have the same issue, you too. 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. Free cell game for mac.

This of course triggers a restart of Docker Engine and Kubernetes, but now nothing starts up. Aha, I was not aware of the Factory reset button inside the preferences and proceeded to remove the app from Applications/ before installing it again. Not entirely sure how one is supposed to actually uninstall apps from a Mac. 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 reset daemon settings in hopes that it would trigger some other resets and hopefully be able to start up again. Last option I see is to try and do a Uninstall from within the preferences menu.

Clicked it, looks a bit stuck as well. Could it be because Docker and Kubernetes aren't starting properly, or at least Docker Engine? I chose a bold move and force quit the hyperkit process while the uninstall window was open, since it looked like it was stuck. That gave me a message almost immediately stating the uninstall was successful. Well, that was unexpected. 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. Still looking good. $ docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES Kubernetes also works!

How I was able to re-install Docker Go to Docker preferences, click Reset -> Uninstall. While the bar is stuck, open Activity Monitor and force quit hyperkit. 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 had the exact same issue, namely Kubernetes being stuck in the 'Kubernetes is starting.' State after upgrading to 18.05.0-ce-mac67 (25042). What solved it for me was: Preferences => Reset => Reset Kubernetes cluster.

However, after that I got The connection to the server localhost:6443 was refused - did you specify the right host or port? When trying to use Kubectl.

Simply restarting Docker for Mac from the main menu fixed that and now everything is back up and running. So to summarize: • Click on the Docker icon, select Preferences, select Reset, click on Reset Kubernetes cluster • Click on the Docker icon, click on Restart Hope this helps in other cases as well. FWIW, this is still happening (it may be indeed related to switching the current-context, but not really clear why): Version 18.05.0-ce-mac67 (25042) 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 current-context pointing to something other than docker-for-desktop during an update (or a restart?) then Docker for Mac gets confused and tries to install pods to the wrong cluster. To verify this, after K8s started successfully, I switched context to another (work-related) cluster; did a Docker/Restart and observed the 'Kubernetes starting.'