-
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
hyperkit start: Could not find an IP address for 6a:c7:25:8a:7f:2b #1926
Comments
Can you see if there are any entries in the |
@r2d4 Yep, looks like there are two entries. I've since gone back to running minikube using virtualbox, which may be relevant to its contents:
|
Hey folks. I rebuilt First attempt, I get this curious error (curious because my laptop has over 50GB free; I suspect the error is referring to something else):
So I try the same command again, and it gets past that point. But now I get a different error, a permissions issue with getting ssh going (it can't read id_rsa because it's owned by root?):
Here are the contents of
I had installed Is there an obvious path to victory here? Wondering what I'm missing. Thank you! |
edit: can't reproduce anymore after wiping -- I have the same error message as the OP as soon as I try to restart a stopped minikube VM after a macOS reboot (and only in that case):
It should be mentioned that <mac_addr> is different after every invocation of
|
I can only get it to work using
Repro steps:
Version: $ uname -a |
Did you forget to set the |
@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. |
Thanks for the update! We should add an error that helps track down when you forget to set setuid. |
This should be fixed with #2215 |
@dlorenc the original issue was not about permissions, rather about this error:
Can we please reopen? |
Experiencing this as well... Only occurred after starting an initially working cluster then restarting my computer.
Some logs from start:
|
After running |
FWIW, I tried making a new machine (which starts up fine), stopping it, copying the old machine's minikube.rawdisk, id_rsa and id_rsa.pub files to the new one. After doing this, the new machine reports the same Also, of note, I don't see any |
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 |
I observed minikube survives OS restarts if it is shut down with |
same issue,
any updates ? |
@dfang Have you tried fiddling with |
@zoidbergwill what do you mean by fiddling ... here is the contents of the file:
|
I am experiencing the same issue after an unexpected shutdown. |
UPDATE: This means that the manual fix/workaround would be to simply delete the |
@jwandrews seems to me that if #2417 did fix this issue, it only would as a side effect of re-assigning the same ip address. If, for example, |
@huguesalary ahhh good to know. thanks |
BTW, it appears that the specific failure case I mentioned in #1926 (comment) is still a problem in the latest release. |
I'm also experiencing the same problem and came from #2430 OS: MacOS 10.13.6 High Sierra
I found now I'm having this error message:
content of my /var/db/dhcpd_release:
I removed this section, still cannot start |
I believe this is fixed with the latest hyperkit driver, released with v0.34.0. If you are running into this, please try running:
Then run If this is still broken, please re-open the bug, and include the output of:
Thanks! |
I still have the same issue $ ls -la $(which docker-machine-driver-hyperkit)
-rwsr-xr-x 1 root wheel 27779836 Mar 12 17:51 /usr/local/bin/docker-machine-driver-hyperkit As I found out the issue is related to Cisco AnyConnect client. When I turn off corporate VPN the error goes away. |
|
I don't get why this issue is closed while a few people still facing this issue like myself.
|
Anecdotal, but these errors seem to occur when resources (memory, disk) are underallocated/unavailable. The defaults (CPUs=2, Memory=2048MB, Disk=20000MB) work though. |
hi i'm getting the same issue too, i'd tried installing different hyperkit driver versions though, i'll not work ):
|
I got this error when working over VPN.
|
I read all the above comments. Tried below steps,
Also ran, I still get the same error and I am not connected to VPN too. |
Based on @paljsingh's suggestion, I turned off my VPN connection and it worked. Haven't debugged the root cause but I now have:
|
Is this a BUG REPORT or FEATURE REQUEST?: Bug
Please provide the following details:
Environment:
Minikube version: 0.22.0
What happened:
Cluster did not start:
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 getdocker-machine-driver-hyperkit
, I'll try using that one.The text was updated successfully, but these errors were encountered: