minikube: hyperkit start: Could not find an IP address for 6a:c7:25:8a:7f:2b
Is this a BUG REPORT or FEATURE REQUEST?: Bug
Please provide the following details:
Environment:
Minikube version: 0.22.0
- OS: macOS 10.12.6
- VM Driver: hyperkit
- ISO version: minikube-v0.23.3.iso
- Install tools:
- Others:
What happened: Cluster did not start:
$ minikube start --vm-driver hyperkit -v 10
Starting local Kubernetes v1.7.5 cluster...
Starting VM...
Found binary path at /usr/local/bin/docker-machine-driver-hyperkit
Launching plugin server for driver hyperkit
Plugin server listening at address 127.0.0.1:58797
() Calling .GetVersion
Using API Version 1
() Calling .SetConfigRaw
() Calling .GetMachineName
(minikube) Calling .GetState
(minikube) Calling .Start
(minikube) Generated UUID 23bf5b8b-93fe-11e7-b603-784f43517719
(minikube) Generated MAC 6a:c7:25:8a:7f:2b
(minikube) Starting with cmdline: loglevel=3 user=docker console=ttyS0 console=tty0 noembed nomodeset norestore waitusb=10 systemd.legacy_systemd_cgroup_controller=yes base host=minikube
E0907 11:56:39.075265 54829 start.go:143] Error starting host: Error starting stopped host: IP address never found in dhcp leases file Temporary Error: Could not find an IP address for 6a:c7:25:8a:7f:2b
Temporary Error: Could not find an IP address for 6a:c7:25:8a:7f:2b
[... snip a ton of these errors...]
What you expected to happen: The cluster starts normally.
How to reproduce it (as minimally and precisely as possible): See above command
Output of minikube logs (if applicable):
Anything else do we need to know:
I built docker-machine-driver-hyperkit myself, but got the minikube binary from the latest official release here on Github. If there’s a more official place to get docker-machine-driver-hyperkit, I’ll try using that one.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 9
- Comments: 46 (18 by maintainers)
~The problem is~ In my experience, this problem has been that the
hyperkit.pidfile (e.g.~/.minikube/machines/minikube/hyperkit.pid) is taken as gospel, and the PID recorded in the file is not validated as a runninghyperkitprocess. This is why the problem shows up when you e.g. reboot without first stoppingminikube. When I get a little bit of time, I’m planning to take a deeper dive into the source. My first superficial search seems to indicate that the bug is actually in upstream Moby, but I don’t have much confidence in that guess.UPDATE: This means that the manual fix/workaround would be to simply delete the
hyperkit.pidfile and try starting again.After running
minikube deletethenminikube start --vm-driver hyperkitI am back into a working state.I’ve just run into this issue, also (to quote above)
I observe (a) stopping and restarting a hyperkit-based minikube machine regenerates the mac address (b) after restarting the osx host, the hyperkit-based minikube machine will not update /var/db/dhcpd_leases at all.
It seems that a hyperkit-base minikube will not survive a host reboot, and that if you reboot, you must
minikube deleteand rebuild. At least with v0.24.1I still have the same issue
As I found out the issue is related to Cisco AnyConnect client. When I turn off corporate VPN the error goes away.
Based on @paljsingh’s suggestion, I turned off my VPN connection and it worked. Haven’t debugged the root cause but I now have:
I got this error when working over VPN.
minikube startworks after I disconnect from the VPN.I believe this is fixed with the latest hyperkit driver, released with v0.34.0. If you are running into this, please try running:
curl -LO https://storage.googleapis.com/minikube/releases/latest/docker-machine-driver-hyperkit && sudo install -o root -g wheel -m 4755 docker-machine-driver-hyperkit /usr/local/bin/Then run
minikube delete && minikube start --vm-driver=hyperkitto recreate your VM.If this is still broken, please re-open the bug, and include the output of:
ls -la $(which docker-machine-driver-hyperkit)Thanks!
I don’t get why this issue is closed while a few people still facing this issue like myself.
@antoineco Is there a less intrusive option than having to delete the VM as per your comment. My issue is sometimes having the minikube VM failing to start after putting the Mac to sleep. Deleting the VM would make it impossible to continue working existing clusters on minikube.
Would love to hear if there is anything else I can try?
Dear @antoineco, I’ve had problem with HyperKit driver but it IMO was solved by disabling VPN driver. Now I no have problem. Thank you.
@antoineco Thank you for your answer! Sure I’ve tried (many times) do it with have no a result. But when I disabled the ExpressVPN it did worked May be my steps will be useful to somebody:
@antoineco Indeed, merci gamin. When replacing my steps:
by:
then it works fine, and without sudo.
It also works fine using the official version v0.23.0.
I’ve managed to make it work temporarily by deleting
hyperkit.pidand emptying/var/db/dhcpd_leases. But this issue comes back quite often.