search

pires / kubernetes-vagrant-coreos-cluster

Kubernetes cluster (for testing purposes) made easy with Vagrant and CoreOS.
Apache License 2.0
597 stars 205 forks source link

node NotReady after docker.service restart #227

Open 123batman opened 7 years ago

123batman commented 7 years ago

vagrant up

kubectl get nodes

NAME           STATUS                     AGE
172.17.8.101   Ready,SchedulingDisabled   3m
172.17.8.102   Ready                      1m

core@node-01 ~ $ sudo systemctl restart docker.service (or reboot node-01 VM)

kubectl get nodes

NAME           STATUS                     AGE
172.17.8.101   Ready,SchedulingDisabled   4m
172.17.8.102   NotReady                   2m

And it never changes back to Ready status.

agallo73 commented 6 years ago

this is a great problem also for me. If i halt the vm I have to recreate all the configurations each time and thus the image is unusable. Also when wi fi goes down I have the same problem. Is there some work around to use to solve this terrible problem? Thanks in advance.