minikube start: apiserver unhealthy: <nil>: Error #3522
Comments
|
Same but on OS X 10.13.6 |
|
Do you mind trying again with minikube v0.33.0? We've made a few changes which might help here. If it still fails, can you attach the apiserver logs? I suspect it may be crash-looping:
|
|
@tstromberg look good |
|
@tstromberg I tried it again with minikube v0.33.0 but on my MacBook (OS X 10.13.6) with vm driver: virtualbox. it starts properly! $ minikube stop
Stopping local Kubernetes cluster...
Machine stopped.
$ minikube start
Starting local Kubernetes v1.13.2 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Stopping extra container runtimes...
Machine exists, restarting cluster components...
Verifying kubelet health ...
Verifying apiserver health ....
Kubectl is now configured to use the cluster.
Loading cached images from config file.
Everything looks great. Please enjoy minikube!
$ minikube status
host: Running
kubelet: Running
apiserver: Running
kubectl: Correctly Configured: pointing to minikube-vm at 192.168.99.100 |
|
I'm still getting the error. I'm running minikube v0.33.1 in macOs 10.13.6. It boots up normally but after creation and attempting to make some deploys, it crushes and stops working. |
|
I'm getting the same error - everything looks fine but then the apiserver fails - the dashboard freezes, commands don't work. I'm on v0.33.1 in Mac 10.14.2 |
|
I can confirm on 10.13.6 apiserver shows error and everything stop working some time after deployment. |
|
Not sure if that will help. Logs from |
|
The same thing, I'm getting these errors over and over after some time which is very frustrating. I don't do anything special except running minikube helm & istio. It's also not a resource problem as I assigned 8 cores and 20gb of ram. |
|
Very similar setup as @kamilgregorczyk; with helm and istio running on osx (virtualbox). i started minikube with 6 cpu and 8192 of ram; but it looks like the apiserver gets overloaded. and afterward its followed up with a bunch of TLS handshake errors that look like this: then more errors that say 8443 connect: connection refused... and the last couple messages before the container restarts is: |
|
Same here running minikube on Manjaro with kvm2 driver. Only running Istio on the cluster. Kubernetes v1.13.0 and Istio 1.1.8 |
|
Think I fixed this one by applying more memory to the minikube vm as documented here: https://istio.io/docs/setup/kubernetes/prepare/platform-setup/minikube/ |
|
I applied 20gbs.. |
|
@kamilgregorczyk Did you set the configuration in Virtual Box? |
|
Yes |
|
Same here with 12 GB memory |
|
I am having the same problem using Kubernetes on minikube. The CPU is cycling up to 100% as the apiserver is cycling between status Running, Error, and Stopped. I have allocated 16GB and 4 CPUs to Docker and changing this up and down doesn't affect the problem. I can't even run the kubectl get pods command without getting back one of these two errors, seems to depend on the state of apiserver at the time: Error from server: rpc error: code = Unavailable desc = transport is closing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Please provide the following details:
Environment:
Minikube version (use
minikube version): v0.32.0cat ~/.minikube/machines/minikube/config.json | grep DriverName): virtualboxcat ~/.minikube/machines/minikube/config.json | grep -i ISOorminikube ssh cat /etc/VERSION): minikube-v0.32.0.iso"What happened:
minikube start, apiserver unhealthy: : Error
after waiting some minutes
apiserver become running
What you expected to happen:
minikube should start properly
How to reproduce it (as minimally and precisely as possible):
start minikube after stopped
Output of
minikube logs(if applicable):Anything else do we need to know:
The text was updated successfully, but these errors were encountered: