-
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
machine didn't return an IP after 120 seconds #5895
Comments
I've got no idea off-hand. Perhaps a firewall may be getting in the way of the VM getting a DHCP lease? |
I have reinstall with the new Ubuntu 18.04 LTS from scratch for my computer, but I get the same error. I tried to flush all the iptables rules. But it still doesn't work. Is there any other firewall installed in the Ubuntu will block the minikube? Could it be related to the Hardware problem? I found out that if I intercept the deploying process, I can see the minikube-net for this time.
I also tried to build it on the Windows 10 with hyperv, It seems that I have got the same problem. The vm cannot get the proper ip. I don't know if it is the problem related to the hardware, but, I can deploy with the docker desktop kubernetes cluster. |
I don't yet have a root cause, but this issue appears to be a duplicate of #3566, do you mind if we move the conversation there? Ths way we can centralize the content relating to the issue. If you feel that this issue is not in fact a duplicate, please re-open it using Thank you for reporting this! |
The exact command to reproduce the issue:
minikube start --vm-driver=kvm2 --alsologtostderr -v=7
The full output of the command that failed:
The output of the
minikube logs
command:The operating system version:
Linux Mint 19.2
I also have upgrade the kvm2 machine driver
Here are my env:
The text was updated successfully, but these errors were encountered: