vmwarefusion mount: attempted to get host ip address for unsupported driver

[smebberson]

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

Bug report.

Please provide the following details:

Environment:

Minikube version (use minikube version): v0.25.2

• OS (e.g. from /etc/os-release): MacOS v10.13.4 (17E199)
• 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 ISO or minikube ssh cat /etc/VERSION): v0.25.1
• Install tools:
• Others:
  The above can be generated in one go with the following commands (can be copied and pasted directly into your terminal):

minikube version
echo "";
echo "OS:";
cat /etc/os-release
echo "";
echo "VM driver": 
grep DriverName ~/.minikube/machines/minikube/config.json
echo "";
echo "ISO version";
grep -i ISO ~/.minikube/machines/minikube/config.json

What happened:

I ran minikube mount ~/Developer/project/folder/:/mnt/project/folder and got the error:

E0507 15:39:28.242867   24753 mount.go:113] Error getting the host IP address to use from within the VM:  Error, attempted to get host ip address for unsupported driver

What you expected to happen:

I expected it to work properly.

How to reproduce it (as minimally and precisely as possible):

Start minikube on MacOS with VMWare Fusion with:

• minikube start --vm-driver=vmwarefusion
• minikube mount ~/Developer/project/folder/:/mnt/project/folder

Output of minikube logs (if applicable):

N/A

Anything else do we need to know:

Looks like it needs to be implemented here

minikube/pkg/minikube/cluster/cluster.go

Line 299 in f5d9455

func GetVMHostIP(host *host.Host) (net.IP, error) {

[cmbernard333]

I am bumping this issue. I am also seeing it and I am unable to start my minikube machine.

executing: /Applications/VMware Fusion.app/Contents/Library/vmrun -gu docker -gp tcuser runScriptInGuest /Users/christianbernard/.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
E0606 12:19:50.159198 868 start.go:159] Error starting host: Error creating host: Error executing step: Creating VM.

[fenos]

I confirm this behaviour as well, it just crashes, without being able to start.
Same stack trace as @cmbernard333

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.