-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Exiting due to GUEST_START: wait 6m0s for node: wait for healthy API server: apiserver healthz never reported healthy: timed out waiting for the condition #10343
Comments
Hey @BioGeek thanks for opening this issue. Unfortunately I'm not very familiar with WSL, but I found additional issues/blog posts that may be useful:
Please let us know if you find anything that resolves your issue, and if not we can keep trying to debug! |
@BioGeek Is this still an issue you're facing? |
@spowelljr I upgraded A ticket is opened (kubernetes/website#26998) to update the blog post that I am following to show the correct commands to install For completness sake, the output of Details
|
I'm having the same Issue. My workaround is running But is way slower. |
Yeah properly supporting WSL with the docker and none drivers is in our roadmap for this year. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
Hi @priyawadhwa , @BioGeek I am running it on mac with hyperkit
Exiting due to GUEST_START: wait 6m0s for node: wait for healthy API server: controlPlane never updated to v1.21.2
|
Hi @hardik-dadhich, can you try running |
Doesn't work. I just cannot start it ,no devops for me ig. |
this worked for me |
Update : Fixed.
|
Hi @BioGeek, I see that kubernetes/website#26998 is now closed. Are you still experiencing this issue? |
@klaases When I opened this issue, I was still using WSL. I have since switched to using Linux full time, so this issue is no longer relevant for me. Hence, I will close this issue. |
have you tried to implement using terraform . I'm facing the same issue . Would you mind providing the code? |
This worked for me too |
Steps to reproduce the issue:
I am following this blogpost to setup Kubernetes and Minikube on WSL2 on Windows 10.
OS: Windows 10 Version 1909 build 18363.1256
WSL2 distro: Ubuntu 20.04 LTS
I can follow the above mentioned blogpost until Minikube: the first cluster.
Instead of
sudo minikube start --driver=none
I just dominikube start
, but I get the following error:This seems a similar error as in #9556, so to answer a few questions from there as well:
do you happen to use a VPN or a proxy ?
In a previous step when following the blogpost, a proxy was set up to access a dashboard.
do you have a custom DOCKER_HOST
echo $DOCKER_HOST
retuns an empty stringdo you mind sharing
env | grep DOCKER
env | grep DOCKER
returns nothingFull output of failed command (
minikube start
with "--alsologtostderr" flag)minikube.log
Optional: Full output of
minikube logs
command:minkube2.log
The text was updated successfully, but these errors were encountered: