-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Users directory is not shared with Hyper-V VM #518
Comments
Experiencing the same issue when using xhyve driver on Mac. |
@numbsafari you should make sure that you using the latest xhyve driver https://github.com/zchee/docker-machine-driver-xhyve/releases/tag/v0.2.3 The behavior for the xhyve driver was only added in v0.2.3 |
Got it. I think I'm having some other issue related to |
@RaeesBhatti it looks like hyper-v doesn't come with any built in folder host to guest folder sharing. We'll have to implement something for this ourselves. |
@dlorenc Docker for Windows has an option to share drives with the VM. I think it would be better to ask them for help. Maybe @FrenchBen can share some insight! |
"The Linux VM used for Docker for Windows uses SMB/CIFS mounting of the host filesystem." excerpt from Docker for Windows docs. |
@RaeesBhatti that's exactly right - there's a bit of magic to make work though :P |
Is there going to be a fix for this in the near future? Or nobody is interested? |
We'd definitely like to fix this, we just don't have much Windows expertise :( I'm happy to help out any way I can if someone wants to give this a try. |
We have recently added a |
Closing as the |
Minikube version (use
minikube version
):minikube version: v0.8.0
Environment:
hyperv
Docker version 1.11.1, build 5604cbe
What happened:
The user home directory
C:/Users/myuser
is not shared with the minikube VM.What you expected to happen:
The user home directory should have been shared with the VM.
How to reproduce it (as minimally and precisely as possible):
Start minikube with
hyperv
driver and try to access the user directory from the VM.Anything else do we need to know:
This is a follow up on #467 and #465
The text was updated successfully, but these errors were encountered: