Minikube mount fails silently

[RoBorg]

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

Please provide the following details:

Minikube version: v0.25.0

• OS: Windows 10
• VM Driver: Hyper-v
• ISO version: v0.23.6

What happened:
Mounted directory is empty on the minikube machine but no errors are visible

What you expected to happen:
Minikube should show an error (and preferably exit)

How to reproduce it:
Run minikube mount -v10 C:\my-project:/projects/my-project

Mounting C:\my-project into /projects/my-project on the minikube VM
This daemon process needs to stay alive for the mount to still be accessible...
ufs starting

Sometimes minikube fails to create the mount properly, but there's no indication of this from the command unless you run in verbose mode, e.g. minikube mount -v10 .....

It should display an error message and probably exit as it doesn't seem to retry at all.

[cz8s]

I had the same problem.
Realized it was the firewall on my mac that dropped the connection.
But the line on how to reproduce really helped finding the issue. <3

[marburps]

I have the same issue on Windows 10 OS.

[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
/remove-lifecycle stale

[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