minikube: 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
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
$ minikube version
minikube version: v1.17.1
commit: 043bdca07e54ab6e4fc0457e3064048f34133d7e
$ docker version
Client: Docker Engine - Community
Cloud integration: 1.0.4
Version: 20.10.0
API version: 1.41
Go version: go1.13.15
Git commit: 7287ab3
Built: Tue Dec 8 18:59:53 2020
OS/Arch: linux/amd64
Context: default
Experimental: true
Server: Docker Engine - Community
Engine:
Version: 20.10.0
API version: 1.41 (minimum version 1.12)
Go version: go1.13.15
Git commit: eeddea2
Built: Tue Dec 8 18:58:04 2020
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: v1.4.3
GitCommit: 269548fa27e0089a8b8278fc4fc781d7f65a939b
runc:
Version: 1.0.0-rc92
GitCommit: ff819c7e9184c13b7c2607fe6c30ae19403a7aff
docker-init:
Version: 0.19.0
GitCommit: de40ad0
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T12:50:19Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/amd64"}
Unable to connect to the server: dial tcp 192.168.49.2:8443: i/o timeout
I can follow the above mentioned blogpost until Minikube: the first cluster.
Instead of sudo minikube start --driver=none I just do minikube start, but I get the following error:
$ minikube start
π minikube v1.17.1 on Ubuntu 20.04
β¨ Automatically selected the docker driver
π Starting control plane node minikube in cluster minikube
πΎ Downloading Kubernetes v1.20.2 preload ...
> preloaded-images-k8s-v8-v1....: 491.22 MiB / 491.22 MiB 100.00% 7.38 MiB
π₯ Creating docker container (CPUs=2, Memory=6300MB) ...
π³ Preparing Kubernetes v1.20.2 on Docker 20.10.2 ...
βͺ Generating certificates and keys ...
βͺ Booting up control plane ...
βͺ Configuring RBAC rules ...
π Verifying Kubernetes components...
β Enabling 'default-storageclass' returned an error: running callbacks: [Error making standard the default storage class: Error listing StorageClasses: Get "https://192.168.49.2:8443/apis/storage.k8s.io/v1/storageclasses": dial tcp 192.168.49.2:8443: i/o timeout]
π Enabled addons: storage-provisioner
β 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
πΏ If the above advice does not help, please let us know:
π https://github.com/kubernetes/minikube/issues/new/choose
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_HOSTretuns an empty string -
do you mind sharing
env | grep DOCKERenv | grep DOCKERreturns nothing
Full output of failed command ( minikube start with ββalsologtostderrβ flag)
minikube.log
Optional: Full output of minikube logs command:
minkube2.log
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 1
- Comments: 15 (3 by maintainers)
Hi @hardik-dadhich, can you try running
minikube delete --all --purgeand then starting minikube again after, I believe that should solve the issue youβre facing.Yeah properly supporting WSL with the docker and none drivers is in our roadmap for this year.
@spowelljr I upgraded
minikubefromv1.17.1tov1.19.0and tried again, but I still have the same error.A ticket is opened (https://github.com/kubernetes/website/issues/26998) to update the blog post that I am following to show the correct commands to install
minikubeon WSL2. Once that issue gets resolved I will report back here.For completness sake, the output of
minikube start --alsologtostderr -v=4:Details