-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Comments
Any update, work-around on this one, please ? |
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 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 |
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! |
/reopen Doesn't work. That other post basically says to switch off VPN and use |
@chainhead: Reopened this issue. In response to this:
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. |
@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? for more information on the docker driver checkout: |
@chainhead I haven't heard from you, do you still have this issue ? |
No, I gave up. I ended up using Virtual box as driver. Please close this. |
Steps to reproduce the issue:
minikube start --vm-driver hyperkit
Full output of failed command:
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.@tstromberg
The text was updated successfully, but these errors were encountered: