hyperkit: IP address never found in dhcp leases file Temporary Error: Could not find an IP address for <mac> #4206
Comments
tstromberg
changed the title
|
This is a duplicate of #1926 - the solution is to upgrade your hyperkit driver:
Then run If this is still broken, please re-open the bug, and include the output of:
I will make sure we provide a more user friendly error message for this case. Thanks! |
tstromberg
added
cause/vm-driver
|
I've tried what you suggest many times, but I'm still having the exact same issue. $ ls -la $(which docker-machine-driver-hyperkit) |
|
Thanks for the update! Do you mind providing updated output for The newer version of the hyperkit driver (which you appear to be on) should log a bit more information on what DHCP entries it finds in that file, which would be very useful here. |
tstromberg
added
priority/awaiting-more-evidence
|
Regrettably, there isn't enough information in this issue to make it actionable, and a long enough duration has passed, so this issue is likely difficult to replicate. If you can provide any additional details, such as:
Please feel free to do so at any point. Thank you for sharing your experience! |
|
This might be a naive suggestion to the source of the problem here, but on my Mojave install there is no |
|
If you are running into this, please share the output of:
and:
Thanks! |
|
Also experiancing this issue. OS: macOS Mojave 10.14.6
(feel like I'm doing that wrong 😟 ) As @snoopdouglas mentioned using Mojave there is |
|
I'm also having the same issue using Mojave, The output of And the output of
and like other folks in this thread, I don't have a |
|
@rkrdo Are you using a vpn at the same time, or have a vpn client installed? |
|
Same with me too. Missing Details
Note:
Some digging I did (if it helps) -
Please let me know if you need any other information to fix this issue, happy to help. I can also voluntary to fix this issue once we can identify the root cause. |
@colangelo thank you for the suggestion! it turned out it to be Little Snitch that was causing preventing |
|
Thanks @rkrdo, good to know! I also have Little Snitch installed, and most of the times i have no issues, but sometimes especially a few months ago, if i'd recently connected or disconnetted from the vpn i was getting that error. My opinion is that this issue is probably related to one ore more third party software that interact with the network stack, and interact badly with minikube's dhcp (or hyperkit's). |
tstromberg
removed
the
triage/needs-information
tstromberg
added
priority/important-longterm
|
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
k8s-ci-robot
added
lifecycle/rotten
priyawadhwa
added
lifecycle/frozen
|
I encountered this issue after upgrading from catalina to big sur. Tried a bunch of stuff and eventually got it working again. Not sure exactly what I did to fix it, but I can show everything: foo@bar$ brew reinstall hyperkit
foo@bar$ brew link hyperkit
foo@bar$ sudo chown root:wheel /usr/local/Cellar/hyperkit/0.20200908/bin/hyperkit
foo@bar$ sudo chmod u+s /usr/local/Cellar/hyperkit/0.20200908/bin/hyperkit
foo@bar$ brew reinstall docker-machine-driver-hyperkit
foo@bar$ sudo chown root:wheel /usr/local/opt/docker-machine-driver-hyperkit/bin/docker-machine-driver-hyperkit
foo@bar$ sudo chmod u+s /usr/local/opt/docker-machine-driver-hyperkit/bin/docker-machine-driver-hyperkit
foo@bar$ sudo rm /var/db/dhcpd_leases
foo@bar$ sudo touch /var/db/dhcpd_leases
foo@bar$ minishift stop
foo@bar$ minishift delete --force --clear-cache
foo@bar$ rm -rf ~/.minishift
foo@bar$ brew install --cask --force minishiftGo to System Preferences > Security & Privacy > Firewall > [Firewall Options] > [ ] Enable stealth mode And disable stealth mode if enabled. foo@bar$ minishift start --show-libmachine-logs -v5 --network-nameserver 8.8.8.8I dont know for sure, but I suspect the fix was |
|
Same issue in Big Sur. I tried disconnecting from VPNs, tried the steps from @hughpearse but no luck |
|
I am still having teh same issue with BigSur .. it seems noting worked form me.. have any one fine a solution for that |
|
Same issue on Catalina. Have upgraded hyperkit, stopped vpn, touched /var/db/dhcpd_leases. But it works when I change the driver to docker |
|
not working for me as well. |
|
for my case, I had my corporation antivirus running (particularly McAfee), which was blocking the creation of |
|
Running MacOS Big Sur 11.6.2 in a corporate environment which has the I created a new pf rules file Unsure whether the Reference the rules file in /etc/pf.conf: To reload pf using the updated rules: Cleared everything down with The minikube starts successfully. |
|
Hello, colleagues.
|
|
@georhiireva - There is typo in your second command with the work minishift and cache |
@cr-tech-repo , thanks, fix it |
@edrandall I get a syntax error while enabling the firewall. Any idea which part might be causing it?
I am on MacOS Catalina 10.15.7. |
|
probably a mismatched quote somewhere, could be in pf.conf or any of your anchor files. |
|
I've tried all the solutions with a Mac M1 with Monterey and the x86 (Rosetta) execution mode and I couldn't get minishift or minikube working. It's always something at the network adapter. My Mac seems to have the leases at /var/db/dhcpclient/leases and not under /var/db/dhcp_leases anyway. |
|
Facing this issue too on BigSur Mac - tried all tricks about to no avail |
|
Try the following packet filter rules: |
|
This is biting me as well. I followed up most of suggestions including the /etc/pf.anchors. I cannot turn off the firewall as my company Mac is under control of Falcon. Mac is Intel, Monterey 12.4. As of 2022-07-18, as far as I can tell, minikube_logs_1b004fc441daa6a7016058454b974cf8421ba12a_0.log |
|
I'm on Mac Monterrey and saw the note about the dhcp_leases file not being there (true) but /var/db/dhcpclient containing IP information. I'm in a crunch to get through this K8s tutorial, so I thought I'd try something down and dirty and copy one of the files from the dhcpclient to /var/db/dhcpd_leases and see if that worked -- but it couldn't parse XML, so I'm stuck again. I'll clean up my hack and pull the logs - but the issue remains that there is no such file as dhcpd_leases 😿 Failed to start hyperkit VM. Running "minikube delete" may fix it: creating host: create: Error creating machine: Error in driver during machine creation: IP address never found in dhcp leases file Temporary error: unable to parse line: <?xml version="1.0" encoding="UTF-8"? |
|
It fixed for me after I uninstalled Falcon Sensor. (macOS-2.6.1) |
|
I'm going to investigate starting |
|
/assign |
and others
Hi,
minikube does not start on my mac, I tried multiple times to remove and reinstall Docker Desktop and docker-machine-driver-hyperkit without solving the problem.
It's not related to version 1.0.1, because the problem was present also with version 1.0.0 and maybe also with previous versions that I haven't tested.
When I lanch minikube the /usr/local/bin/docker-machine-driver-hyperkit process appears in the process list, does not use CPU, and it's still present for some time after the command exited.
Can you help me?
The exact command to reproduce the issue:
The full output of the command that failed:
The output of the
minikube logscommand:The operating system version:
macOS Mojave 10.14.4 (18E226)
Darwin mac.local 18.5.0 Darwin Kernel Version 18.5.0: Mon Mar 11 20:40:32 PDT 2019; root:xnu-4903.251.3~3/RELEASE_X86_64 x86_
The text was updated successfully, but these errors were encountered: