-
Notifications
You must be signed in to change notification settings - Fork 120
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
"Kubernetes is starting…" state never ends #2990
Comments
I have the same problem when update to the version 18.05.0-ce-mac67 (25042).
Diagnostic logs: |
Experiencing the same after upgrading to macOS 10.13.5. Also see #2985 |
I had exactly the same scenario and issue-- even rebooting didn't help. Simply doing the "Reset Kubernetes cluster" on the Reset tab resolved the issue for me. (I didn't have to go so far as to reset to factory defaults.) |
I didn't realize Reset was a tab! I thought it's a button that would reset everything at once (not just Kubernetes). Resetting the Kubernetes cluster has helped indeed, although I do hope that this is just a one time thing. I was happy to move from minikube to Docker for Mac primarily because minikube releases broke the Kubernetes cluster often. Hopefully this will not be the case with Docker for Mac in the future. |
"Reset Kubernetes cluster" also worked for my case! Thank you so much 😆 |
@plambert your logs have:
and yet
and
I notice that |
I've fixed a bug in the code which failed to notice the node had become |
Hi @djs55 I have tried with my previous |
@tjamet thanks a lot for the speedy confirmation! |
For what it is worth, Kubernetes is now running successfully without your patch @djs55 on version I have edge installed via
Not sure why this works and how it doesn't 'require' your patch, but it something others might try if they need a 'production' build. |
@djs55 I still have "Kubernetes is starting..." running your dmg build. |
I had the same issue, found out my /etc/hosts was empty. Once I restored it original values, Kubernetes is now starting successfully. |
what worked for me is a reset of ALL data, then recreate it all. |
I also have this issue. Kubernetes worked fine one time, but after I had to reboot, it got stuck in "Kubernetes is starting". I tried these steps:
But it still won't start.
|
Yep, getting the same thing. Latest release for macOS (stable). Will test edge too. |
Failing on edge too, tried all means of getting it running (yes I uninstalled homebrew too). Moving back to |
Same as above: stuck in starting after updating to latest macOS release on both stable and edge channels. |
I had it running fine on my mac but but after upgrading my OS to "High Sierra 10.13.6", running into same issue. Have already tried a few different stable and edge versions. |
Same here, testing both versions stable/edge, OS HS 10.13.6 |
Same here as well, at first with the latest stable and now with Edge |
same with macos 10.14 and 18.06.1-ce-mac73 the problem seems to be with etcd:
which does match the interfaces:
|
I found a solution that worked for me, don't change default Docker subnet 192.168.65.0/24 Version 18.06.1-ce-mac73 (26764) |
Try setting swapMiB to 0 in ~/Library/Group Containers/group.com.docker/settings.json, that worked from me |
Hit this issue. After check the "Enable Kubernetes" configuration, it shows "Starting ...". state, but never ends. However, it seems that the k8s cluster has been created and running. ⚡ kubectl cluster-info
Kubernetes master is running at https://kubernetes.docker.internal:6443
KubeDNS is running at https://kubernetes.docker.internal:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'. Environment information:
|
Yet another "worked for me too" here, thanks! Initially I tried to enable Kubernetes from the dashboard - got stuck in the starting phase. Console (app) kept repeating mDNSResponder lines with DNSServiceQueryRecords relating to (com.docker.driv) and process com.docker.driver.amd64-linux saying that it Docker 2.4.0.0 |
I did not allocate enough resources. Once I did, this state cleared after restarting docker. |
|
This worked, for Mac! Thanks |
Docker bottom notification still saying "Kubernetes is starting..." with orange icon, for minutes, while it was working. After 3 to 5 of minutes, it's show "running" with green icon. |
Exactly that ! May I add that here we don't have to delete the hole Removing every entry of the Also had to wait a few minutes as stated here above before the Docker Desktop app showed a green light again for K8s, but the context & local cluster were already working anyway. Environment information: |
or
|
I have this issue on macbook pro M1. |
@sayjeyhi if it still doesn't work, try to find out if 2 versions of Kubernetes are installed. This was my case at the beginning, the Docker Desktop app already install a Kubernetes version, and I installed another one with brew, that linked the bin to the new one, causing problem with Docker App. I uninstalled the brew version, and followed the steps in this issue. |
@KeitelDOG Were you using the M1 preview application? because I did not install k8s with brew |
@sayjeyhi no, I have a regular macbook pro. I was just using the Docker Desktop app that installed automatically kubernetes too. |
Having this issue right now, after trying to Reset the cluster it never started again, just waiting in Starting-state. $ kubectl get pod -A
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system etcd-docker-desktop 1/1 Running 0 2m5s
kube-system kube-apiserver-docker-desktop 1/1 Running 0 2m6s
kube-system kube-controller-manager-docker-desktop 0/1 CrashLoopBackOff 4 3m
kube-system kube-scheduler-docker-desktop 1/1 Running 0 118s $ kubectl -n kube-system logs kube-controller-manager-docker-desktop
# Click Details below to see output
Edit: here's what worked for me, combining information from various comments:
|
@codeclown That worked for me, thank you! |
In Debug mode settings, reseting cluster and cleaning up the docker data helped me. |
This solution worked for me too |
@codeclown Thanks!!! It worked :) |
I'd fixed this previously, and upon upgrading docker desktop, it's back to being broken, with the infinite "starting". Confirmed that @dECRISES solution worked for me in fixing it up again. |
I solved that in my M1 MacBook Air. Commenting it here in case this helps anyone. On Docker Desktop, open Preferences and follow the steps,
After restarting Kubernetes will be enabled. Open terminal and type "kubectl version" to confirm. |
v1.21.2 m1. has the same P |
https://github.com/maguowei/k8s-docker-desktop-for-mac resolveed |
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. |
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
Within a few minutes of starting Docker for Mac, Kubernetes should be available.
Actual behavior
After several hours, it is still 'starting…'
Information
Diagnostic logs
(Uploaded as 804B8977-06D2-4E2A-BB3E-10FBBA99D1F9/20180611-105749)
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: