minikube won't start on macOS Big Sur with VMWare Fusion 12 #9720
Comments
|
/kind support |
k8s-ci-robot
added
the
kind/support
|
I'm having a similar issue. It appears to have something to do with the vmnet-dhcpd-vmnet*.leases files no longer being used in Fusion 12 on Big Sur. If so, more details can be found on VMware's site: https://communities.vmware.com/t5/VMware-Fusion-Discussions/Big-Sur-hosts-with-Fusion-Is-vmnet-dhcpd-vmnet8-leases-file/m-p/2298924 Basically it seems Fusion went from running it's own DHCP server to using Apple's vmnet API. Not sure what the fix is, but hopefully this helps... |
|
Have the same issue |
|
Probably an issue for https://github.com//machine-drivers/docker-machine-driver-vmware
|
|
This does seem to be an issue at least related to docker-machine-driver, but that project appears all but abandoned. I was able to get everything working, and I also have an open ticket with VMware, so hopefully they can make this all a bit less painful, but here's what worked for me. Fusion released an update today that bundles docker-machine-driver-vmware. I have no idea if it's any different, but I'm using it anyway. So I did a complete uninstall of Fusion, removed the docker-machine-driver-vmware that I had installed using brew, and did a clean install of Fusion 12.1.0. It seems that with Big Sur/Fusion 12 vm DHCP leases are written to To fix that, I had to open Fusion, then add the minikube vm to my library, then add the missing network adapter. So in Fusion, Then start minikube again from the command line and check replacing {IP_ADDRESS} and {MAC_ADDRESS} with the correct values from the the Obviously this is super cumbersome, but at least it means a solution exists. Just need to find a way to clean it all up. |
|
Have the same issue |
The docker-machine project is dead, but we can still use patches to the drivers for minikube only (like kvm2 or hyperv) |
|
It was a certain amount of trial and error and 'poking at things', but I was able to follow @itised instructions and specifically add a second 'private to this mac' network adapter that let minikube start. Additional things I found helpful was to start minikube with pretty verbose logging |
|
Same issue. Will try and follow the earlier directions |
|
Prior instructions did not work for me. |
|
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
k8s-ci-robot
added
the
lifecycle/stale
|
/remove-lifecycle stale |
k8s-ci-robot
removed
the
lifecycle/stale
|
there's also a bug report in the machine driver at machine-drivers/docker-machine-driver-vmware#30 and a possible fix in machine-drivers/docker-machine-driver-vmware#31 |
spowelljr
added
the
long-term-support
|
@afbjorklund Looks like the possible fix was approved a while ago by @zarenner. Any ideas how we can get that pushed through? |
|
@allanchau I believe we have included this in the go mod do u mind checking if this has been fixed on master? |
|
@medyagh Do you mean this is already in the latest minikube release or should I update the driver to v0.1.1 and test? |
|
I think you need to build a new version of the minikube only imports the driver for the config (instead of using flags), not for running it |
|
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
k8s-ci-robot
added
the
lifecycle/stale
|
while the bundled driver in Fusion 12.1.2 is still not updated manually installing 0.1.3 via brew does work now: |
|
/remove-lifecycle stale |
k8s-ci-robot
removed
the
lifecycle/stale
Just confirmed this worked for me! Thx @Nothing4You 💟 |
|
Had same issue. I can confirm that Although, got following warning when installing docker-machine-driver-vmware : |
|
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
k8s-ci-robot
added
the
lifecycle/stale
|
/close |
|
@allanchau: 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. |
Minikube version
$ minikube version I1117 09:00:49.386072 45858 translate.go:89] Failed to load translation file for en: Asset translations/en.json not found minikube version: v1.15.0 commit: 3e098ff146b8502f597849dfda420a2fa4fa43f0VMware Fusion version
Steps to reproduce the issue:
minikube start --disk-size 64g --extra-config=apiserver.service-node-port-range=80-32767 --cpus=2 --memory=8192 --vm-driver=vmware --alsologtostderr --v=8Full output of failed command:
W1117 09:12:13.741055 45509 out.go:146] * Suggestion: Try 'minikube delete', and disable any conflicting VPN or firewall software
W1117 09:12:13.741151 45509 out.go:146] * Related issue: hyperkit high sierra + VPN: create host timed out in 120.000000 seconds #7072
I1117 09:12:13.832302 45509 out.go:110]
The text was updated successfully, but these errors were encountered: