Add functionality for nfs mounts/shares

[RobertDiebels]

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

Please provide the following details:

Environment:

Minikube version (use minikube version): v0.25.0

• OS (e.g. from /etc/os-release): Windows 10 Home
• VM Driver (e.g. cat ~/.minikube/machines/minikube/config.json | grep DriverName): virtualbox
• ISO version (e.g. cat ~/.minikube/machines/minikube/config.json | grep -i ISO or minikube ssh cat /etc/VERSION):
• Install tools:
• Others:

What happened:
For the past few days I've been trying to solve an error thrown by Hyperledger Burrow when running in a Kubernetes cluster.
I won't go into too much detail as I've already done so extensively in this issue: hyperledger-archives/burrow#701

The issue comes down to VirtualBox mounting shared folders into Docker with vboxfs this caused LevelDB to throw an 'illegal argument' error. A possible workaround for that issue is mounting shared folders with nfs instead of vboxfs.

Unfortunately mounting with minikube mount is broken on Windows: #2072
So I can't test mounting at all. Let alone mounting as nfs.

What you expected to happen:
N/A

How to reproduce it (as minimally and precisely as possible):
See this repo for the error this feature could fix: https://github.com/RobertDiebels/virtualbox-minikube-illegal-argument

Output of minikube logs (if applicable):

Anything else do we need to know:

[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