-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Description
BUG REPORT
Please provide the following details:
Environment:
Minikube version (use minikube version):minikube version: v0.28.1
- OS (e.g. from /etc/os-release): MacOS 10.13.4 (High Sierra)
- VM Driver (e.g.
cat ~/.minikube/machines/minikube/config.json | grep DriverName): vmwarefusion - ISO version (e.g.
cat ~/.minikube/machines/minikube/config.json | grep -i ISOorminikube ssh cat /etc/VERSION):
v0.28.1 - Install tools:
- Others:
What happened:
"minikube start --vm-driver=vmwarefusion" always fails.
What you expected to happen:
minikube successfully gets started
How to reproduce it (as minimally and precisely as possible):
"minikube start --vm-driver=vmwarefusion" always reproduces the issue.
Output of minikube logs (if applicable):
minikube start --v 10 --vm-driver=vmwarefusion --logtostderr --alsologtostderr
.
.
.
Trying to find IP address in leases file: /var/db/vmware/vmnet-dhcpd-vmnet8.leases
IP found in DHCP lease table: 192.168.43.172
Got an ip: 192.168.43.172
Creating Tar key bundle...
executing: /Applications/VMware Fusion.app/Contents/Public/vmrun -gu docker -gp tcuser directoryExistsInGuest /Users/shindom/.minikube/machines/minikube/minikube.vmx /var/lib/boot2docker
executing: /Applications/VMware Fusion.app/Contents/Public/vmrun -gu docker -gp tcuser CopyFileFromHostToGuest /Users/shindom/.minikube/machines/minikube/minikube.vmx /Users/shindom/.minikube/machines/minikube/userdata.tar /home/docker/userdata.tar
executing: /Applications/VMware Fusion.app/Contents/Public/vmrun -gu docker -gp tcuser runScriptInGuest /Users/shindom/.minikube/machines/minikube/minikube.vmx /bin/sh sudo sh -c "tar xvf /home/docker/userdata.tar -C /home/docker > /var/log/userdata.log 2>&1 && chown -R docker:staff /home/docker"
executing: /Applications/VMware Fusion.app/Contents/Public/vmrun -gu docker -gp tcuser runScriptInGuest /Users/shindom/.minikube/machines/minikube/minikube.vmx /bin/sh sudo /bin/mv /home/docker/userdata.tar /var/lib/boot2docker/userdata.tar
executing: /Applications/VMware Fusion.app/Contents/Public/vmrun -gu docker -gp tcuser enableSharedFolders /Users/shindom/.minikube/machines/minikube/minikube.vmx
executing: /Applications/VMware Fusion.app/Contents/Public/vmrun -gu docker -gp tcuser addSharedFolder /Users/shindom/.minikube/machines/minikube/minikube.vmx Users /Users
executing: /Applications/VMware Fusion.app/Contents/Public/vmrun -gu docker -gp tcuser runScriptInGuest /Users/shindom/.minikube/machines/minikube/minikube.vmx /bin/sh [ ! -d /Users ]&& sudo mkdir /Users; sudo mount --bind /mnt/hgfs//Users /Users || [ -f /usr/local/bin/vmhgfs-fuse ]&& sudo /usr/local/bin/vmhgfs-fuse -o allow_other .host:/Users /Users || sudo mount -t vmhgfs -o uid=$(id -u),gid=$(id -g) .host:/Users /Users
E0723 13:32:57.420865 9409 start.go:174] Error starting host: Error creating host: Error executing step: Creating VM.
: exit status 1.
Retrying.
E0723 13:32:57.420959 9409 start.go:180] Error starting host: Error creating host: Error executing step: Creating VM.
: exit status 1
Anything else do we need to know:
This problem is caused by a bug in fusion VM driver imported from docker/machine. The fix has already been up-streamed (by me) and merged (PR: docker-archive-public/docker.machine#4491). Please import the latest driver code from docker/machine, which would solve this problem in minikube, too.