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: warn user if firewall is blocking #8331
Comments
Could you post the output of |
Sorry for delayed response @sharifelgamal
Minikube Logs below ;
|
The relevant error from your logs is: There is an open issue about it, that I opened about a year ago: #4206 Basically it's a problem in hyperkit with VPNs, so if you need the vpn you could use a different driver (https://minikube.sigs.k8s.io/docs/drivers/) and then you should be able to start minikube with the vpn connected. I'm also using vmware fusion, and so I'm able to go around the problem by using the vmware driver. |
Not just vpns, mcafee firewall can also mess it up, or WiFi sharing |
is there a way to detect in command line is mcafe firewall is running? I would be happy to review a PR that detects this and warns the user. we should at least update the solution message to say check for firewall |
Issues go stale after 90d 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. |
Never noticed your reply, There is also an xml file that contains the firewall rules. I am not allowed to fully share that file unfortunately |
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. |
/close |
@longwuyuan: Closing 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. |
Steps to reproduce the issue:
minikube v1.11.0 on Darwin 10.15.5
▪ KUBECONFIG=/Users/me/.kube/config:/Users/me/myclusters/kubeconfigs/ssdnodes/config:/Users/me/myclusters/kubeconfigs/laptop/kubeadmcluster/config
✨ Using the hyperkit driver based on user configuration
💾 Downloading driver docker-machine-driver-hyperkit:
> docker-machine-driver-hyperkit.sha256: 65 B / 65 B [---] 100.00% ? p/s 0s
> docker-machine-driver-hyperkit: 10.90 MiB / 10.90 MiB 100.00% 431.88 KiB
🔑 The 'hyperkit' driver requires elevated permissions. The following commands will be executed:
Password:
💿 Downloading VM boot image ...
> minikube-v1.11.0.iso.sha256: 65 B / 65 B [-------------] 100.00% ? p/s 0s
> minikube-v1.11.0.iso: 174.99 MiB / 174.99 MiB 100.00% 537.68 KiB p/s 5m3
👍 Starting control plane node minikube in cluster minikube
💾 Downloading Kubernetes v1.18.3 preload ...
> preloaded-images-k8s-v3-v1.18.3-docker-overlay2-amd64.tar.lz4: 526.01 MiB
🔥 Creating hyperkit VM (CPUs=3, Memory=6000MB, Disk=51200MB) ...
🤦 StartHost failed, but will try again: new host: Error attempting to get plugin server address for RPC: Failed to dial the plugin server in 10s
🔥 Creating hyperkit VM (CPUs=3, Memory=6000MB, Disk=51200MB) ...
😿 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 be:fd:7:a:51:e3
💣 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 be:fd:7:a:51:e3
😿 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
The text was updated successfully, but these errors were encountered: