parallels: minikube mount: attempted to get host ip address for unsupported driver

[dcecile]

Running minikube mount with the parallels driver gives this error message:

💣  Error getting the host IP address to use from within the VM: Error, attempted to get host ip address for unsupported driver

According to the docs, this is preferred over relying on driver-specific mounting.

It's an issue for me right now because I can't figure out how to get share folders enabled through the Parallels UI to show up on the Minikube VM.

[afbjorklund]

How to get the host IP is unfortunately not covered by libmachine API at the moment...
That is: how to get the address of the host running minikube, as seen from inside the VM.

There is a workaround in minikube, but it needs driver-specific code in order to do it:

pkg/minikube/cluster/cluster.go#GetVMHostIP

So it needs an entry for parallels, how to find it ?

If you know the command, then please add it here.

[dcecile]

@afbjorklund It seems like the command might not work properly, and that the reliable way to do it is to install Parallels Tools inside the VM first then remotely execute ip address show dev eth1 | grep .... Equivalently, we could use minikube ssh to do remote execution of ip address. (I tested that minikube ssh works with Parallels.)

Actually it seems like the libmachine API might support getting the host IP now: Driver.GetIP

• The Driver is accessible as host.driver after running cluster. CheckIfHostExistsAndLoad
• For the Parallels driver, it's the exact same code path as minikube ssh, since Minikube cluster.CreateSSHShell calls libmachine API Host.CreateSSHClient which calls Parallels Driver.GetSSHHostname which ends up calling Parallels Driver.GetIP

Do you think that it would work to use Driver.GetIP?

[afbjorklund]

As long as you get the host IP and not just the machine IP, it should be fine.
The only driver using GetIP is VMware, and then replaces the last digit with "1".

For instance, for the default VirtualBox the machine IP starts at 192.168.99.100
And the vboxnet0 interface (hostonlyadapter2) normally gets adress 192.168.99.1

https://www.virtualbox.org/manual/ch06.html#networkingmodes

When host-only networking is used, Oracle VM VirtualBox creates a new software interface on the host which then appears next to your existing network interfaces. In other words, whereas with bridged networking an existing physical interface is used to attach virtual machines to, with host-only networking a new loopback interface is created on the host. And whereas with internal networking, the traffic between the virtual machines cannot be seen, the traffic on the loopback interface on the host can be intercepted.

[tstromberg]

This sounds reasonable. PR's welcome!

[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

[tstromberg]

This would require adding parallels support to pkg/minikube/cluster/cluster.go#GetVMHostIP - probably a 1-line fix at most. Help wanted!

[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

[sharifelgamal]

Help still wanted!

/remove-lifecycle rotten

[legal90]

Hi all,
Here is the fix for this issue: #8259