Skip to content
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 mac: could not find an IP address for b2:a1.... #8940

Closed
chainhead opened this issue Aug 8, 2020 · 9 comments
Closed

hyperkit mac: could not find an IP address for b2:a1.... #8940

chainhead opened this issue Aug 8, 2020 · 9 comments
Labels
kind/support Categorizes issue or PR as a support question. triage/duplicate Indicates an issue is a duplicate of other open issue. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@chainhead
Copy link

Steps to reproduce the issue:

  1. minikube start --vm-driver hyperkit

Full output of failed command:

error provisioning host: Failed to start host: creating host: create: Error creating machine: Error in driver during machine creation: IP address never found in dhcp leases file Temporary error: could not find an IP address for b2:a1:b8:52:7:bb

This is the output (trimmed for brevity) of sudo fs_usage -f network -w 2>&1 | egrep 'hyper|Sharing|launchd|socketfilter' | egrep -i 'bind|AF_INET' command. Basically, launchd is not seen in the output.

07:48:22.095635  bind              F=3                                                                                                                                                                                        0.000005   docker-machine-driver-hyperkit.752195
07:48:23.017515  socket            F=7        <AF_INET, SOCK_DGRAM, 0x0>                                                                                                                                                      0.000012   InternetSharing.718101
07:48:23.017740  socket            F=7        <AF_INET, SOCK_DGRAM, 0x0>                                                                                                                                                      0.000010   InternetSharing.718101
07:48:23.017764  socket            F=7        <AF_INET, SOCK_DGRAM, 0x0>                                                                                                                                                      0.000008   InternetSharing.718101
07:48:23.017775  socket            F=7        <AF_INET, SOCK_DGRAM, 0x0>                                                                                                                                                      0.000006   InternetSharing.718101
07:48:23.017961  socket            F=7        <AF_INET, SOCK_DGRAM, 0x0>                                                                                                                                                      0.000009   InternetSharing.718101
07:48:23.017994  socket            F=7        <AF_INET, SOCK_DGRAM, 0x0>                                                                                                                                                      0.000005   InternetSharing.718101
0

@tstromberg

@priyawadhwa priyawadhwa added the kind/support Categorizes issue or PR as a support question. label Aug 12, 2020
@chainhead
Copy link
Author

Any update, work-around on this one, please ?

@priyawadhwa
Copy link

Hey @chainhead sorry for the late response. This looks like a duplicate of #1926

Do you have a VPN enabled? If so, it seems like turning it off fixed it for other minikube users.

@priyawadhwa priyawadhwa added the triage/needs-information Indicates an issue needs more information in order to work on it. label Sep 8, 2020
@chainhead
Copy link
Author

chainhead commented Sep 9, 2020

@priyawadhwa VPN is off.

minikube start --vm-driver hyperkit
😄  minikube v1.12.0 on Darwin 10.15.6
🎉  minikube 1.13.0 is available! Download it: https://github.com/kubernetes/minikube/releases/tag/v1.13.0
💡  To disable this notice, run: 'minikube config set WantUpdateNotification false'

✨  Using the hyperkit driver based on user configuration
👍  Starting control plane node minikube in cluster minikube
🔥  Creating hyperkit VM (CPUs=2, Memory=4000MB, Disk=20000MB) ...
🔥  Deleting "minikube" in hyperkit ...
🤦  StartHost failed, but will try again: creating host: create: Error creating machine: Error in driver during machine creation: IP address never found in dhcp leases file Temporary error: could not find an IP address for 2:12:7e:e6:f8:da
🔥  Creating hyperkit VM (CPUs=2, Memory=4000MB, Disk=20000MB) ...
😿  Failed to start hyperkit VM. "minikube start" 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: could not find an IP address for ea:38:81:be:56:50

💣  error provisioning host: Failed to start host: creating host: create: Error creating machine: Error in driver during machine creation: IP address never found in dhcp leases file Temporary error: could not find an IP address for ea:38:81:be:56:50

😿  minikube is exiting due to an error. If the above message is not useful, open an issue:
👉  https://github.com/kubernetes/minikube/issues/new/choose

@tstromberg

@priyawadhwa priyawadhwa removed the triage/needs-information Indicates an issue needs more information in order to work on it. label Sep 9, 2020
@priyawadhwa
Copy link

Hey @chainhead looks like this issue is a dupe of #4206 -- I'm going to close this issue so that we can centralize the conversation there.

I'd suggest commenting on that issue and also reading through it, there are a few different fixes suggested by other users.

If you think this issue is different, feel free to reopen at any time by commenting /reopen!

@priyawadhwa priyawadhwa added the triage/duplicate Indicates an issue is a duplicate of other open issue. label Sep 9, 2020
@chainhead
Copy link
Author

/reopen

Doesn't work.

That other post basically says to switch off VPN and use docker-machine-driver-hyperkit from Docker Desktop from Mac.

@k8s-ci-robot k8s-ci-robot reopened this Sep 11, 2020
@k8s-ci-robot
Copy link
Contributor

@chainhead: Reopened this issue.

In response to this:

/reopen

Doesn't work.

That other post basically says to switch off VPN and use docker-machine-driver-hyperkit from Docker Desktop from Mac.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@medyagh
Copy link
Member

medyagh commented Oct 28, 2020

@chainhead sorry to hear you still hve this issue, our docker driver has better support for VPN envirinments, have you tried our docker driver ?

Meanwhile have you tried out newest driver Docker Driver with latest version of minikube?
you could try
minikube delete
minikube start --driver=docker

for more information on the docker driver checkout:
https://minikube.sigs.k8s.io/docs/drivers/docker/

@medyagh medyagh added the triage/needs-information Indicates an issue needs more information in order to work on it. label Oct 28, 2020
@medyagh medyagh changed the title minikube won't launch with hyperkit on MacOS because it couldn't get an IP address. hyperkit mac: could not find an IP address for b2:a1.... Oct 28, 2020
@medyagh
Copy link
Member

medyagh commented Nov 11, 2020

@chainhead I haven't heard from you, do you still have this issue ?

@chainhead
Copy link
Author

No, I gave up. I ended up using Virtual box as driver. Please close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question. triage/duplicate Indicates an issue is a duplicate of other open issue. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

4 participants