Docker Community Forums

Share and learn in the Docker community.

Volume mounts in windows does not work

(Tredzko) #102

@ijeweb This was what ended up solving my problem. Very useful post. Thank you!

(Michael Borejdo) #103

I also cannot get drive-sharing to work, trying all different workarounds/solutions mentioned in this post. I also see similar lines in my log as @cmurczek does.
I am running a Windows 10 Pro 14393 VM inside VMWare on a Linux-Host

> [01:41:02.473][NamedPipeServer][Info   ] Start done.
> [01:41:02.489][Notifications  ][Info   ] Docker is running
> [01:41:02.493][Mixpanel       ][Info   ] Usage Statistic: installShowWelcomePopup
> [01:41:02.523][Mixpanel       ][Info   ] Usage Statistic: appRunning
> [01:41:14.200][Auth           ][Info   ] Storing credentials: dockerhost:***********
> [01:41:14.218][NamedPipeClient][Info   ] Sending TryShare(C, dockerhost:**********)...
> [01:41:14.224][NamedPipeServer][Info   ] TryShare(C, dockerhost:**********)
> [01:41:14.347][Cmd            ][Info   ] Share name        C
> [01:41:14.352][Cmd            ][Info   ] Path              C:\
> [01:41:14.357][Cmd            ][Info   ] Remark            
> [01:41:14.362][Cmd            ][Info   ] Maximum users     No limit
> [01:41:14.366][Cmd            ][Info   ] Users             
> [01:41:14.372][Cmd            ][Info   ] Caching           Caching disabled
> [01:41:14.376][Cmd            ][Info   ] Permission        EM-PC-XXX\xxx, FULL
> [01:41:14.380][Cmd            ][Info   ] 
> [01:41:14.384][Cmd            ][Info   ] The command completed successfully.
> [01:41:14.390][Cmd            ][Info   ] 
> [01:41:14.394][SambaShare     ][Info   ] "C" is shared
> [01:41:14.401][SambaShare     ][Info   ] Challenging credentials with host
> [01:41:14.532][SambaShare     ][Info   ] Challenging credentials with host succeeded
> [01:41:14.535][NamedPipeServer][Info   ] TryShare done.
> [01:41:14.538][NamedPipeClient][Info   ] Received response for TryShare
> [01:41:14.552][NamedPipeClient][Info   ] Sending Mount(C, dockerhost:**********)...
> [01:41:14.558][NamedPipeServer][Info   ] Mount(C, dockerhost:**********)
> [01:41:14.562][HyperV         ][Info   ] Mount C
> [01:41:14.681][NamedPipeClient][Info   ] Received response for Mount
> [01:41:14.676][NamedPipeServer][Info   ] Mount done.
> [01:42:00.316][ApiProxy       ][Info   ] proxy >> POST /v1.24/containers/create [rewriteBinds]
> [01:42:01.330][ApiProxy       ][Info   ] Rewrote mount /c/Users/dockerhost:/mnt (volumeDriver=) to /c/Users/dockerhost:/mnt
> [01:42:01.337][ApiProxy       ][Info   ] Failed to Walk to [snapshots e4711dd0efca74a00762491816d64f8012ead703 ro com.docker.driver.amd64-linux proxy http] 9p: No such file or directory
> [01:42:01.349][ApiProxy       ][Info   ] Failed to read proxies/http from snaphshot p9p.MessageRerror{Ename:"No such file or directory"}

(Michael Borejdo) #104

I am not sure what I have changed, but after playing around with some permissions and manually connecting the cifs share in Windows, Docker seems to be able to mount the shares correctly.

(Kevin Busse) #105

I had some issues as well, maybe due to a special case: the PC is in a domain, but I was using a Microsoft Account instead of a domain account. After I dumped the log files from the VM and saw that there is a permission issue I considered using a domain account and it turned out that using an account within the same domain as the PC it actually worked.

I had uses a non-domain account for another reason so I tried converting the Microsoft account back to a local account (remember not to have a domain user with the same name) and it turns out that works quite as well.

I personally stayed with the last solution - I hope this might help somebody else as well.

(Miroki) #106

I’ve spent hours in vein. then your post came to the rescue.
Thank you!

(Goody) #107

Using my work lappy was able to mount at the office on the network. Having no luck at home trying to mount. So does that mean something with Domain permissions?

Tried a few of the things above with no success. Uninstalled/re-installed. Nada. C’est la guerre.

WIN10 v 1607 OS Build 14383.0

Version: 1.12.0
API version: 1.24
Version: 1.12.0
API version: 1.24

(Philicious) #108

As this cost me like 4h to debug and solve:

Symptom: Could see c:\users\myser but not files and no other folders.

In the end it was a AV-integrated Firewall that was active. After deactivating, it worked.

(Synweap15) #109

Marking the Hyper-V (Docker NAT) interface in Kaspersky as “Trusted” worked for me like a charm. Thanks!

(Sclohr) #110

my solution integrated several of the above solutions.

so for me:

  1. change my local windows account password to something that doesn’t have special characters in it.
  2. turn off windows firewall
  3. reset credentials on shared drives and when entering user name prefix with local computer name

that finally did the trick

(Rob Staveley (Tom)) #111

This solved my issue too is where to look for this.

(Hoanglan87) #112

The feature “SMB/CIFS File Sharing Support” is required also, please add this to the document!

(Cmurczek) #113

@friism when I try running the commands you posted a couple posts above

docker run --privileged -it --rm -v /var/run/docker.sock:/var/run/docker.sock -v /usr/bin/docker:/usr/bin/docker alpine sh

docker run --net=host --ipc=host --uts=host --pid=host -it --security-opt=seccomp=unconfined --privileged --rm -v /:/host alpine /bin/sh

chroot /host

mount -t cifs // /C -o username=,password=,noperm

I get a mount error(115): Operation in progress. Pinging results in 100% package loss, traceroute fails. Pinging the Linux VM from Windows works just fine. I have deactivated the Windows FW on the host for the interface, but no improvement. Browsing \\\C from the host works fine, so the share is active and accessible.
I then checked the routing table in the Linux VM and found that there are 2 default GWs configured ( and, which normally is not a good thing and could explain the failing ping and traceroute.

I also found that the system time was way off (22h in the past). Even if everything else would have been ok, Windows would have treated all requests as replay attack and thus rejected them. I manually corrected it, but it might make sense to leverage NTP to ensure proper system time.

(Zhomoki) #114

I’ve been also struggling with this problem for a while and I’ve found a working a solution (at least for me). I have a corporate machine, Windows 10 Enterprise, inside an Active Directory (my account is an AD account). I also created a local admin account to test.

So it’s kind of obvious that the problem is somewhere between the mobylinux and the host windows10. I wanted to try to mount the C drive directly from mobylinux I couldn’t do that so I created a another VM (it was an Ubuntu) on the same network (DockerNAT) and started to play. I just tried to mount the C drive of the host Windows and list it.

The working commands:
mount -t cifs // /mnt/share -o username=<AD_username without domain>,password=<AD_password>
mount -t cifs // /mnt/share -o username=<AD_username without domain>,password=<AD_password>,domain=<AD_domain>
mount -t cifs // /mnt/share -o username=<local_admin_username>,password=<local_admin_passoword>,domain=<machine_name>

The non-working commands:
mount -t cifs // /mnt/share -o username=<AD_Domain>&lt;AD_username without domain>,password=<AD_password>
mount -t cifs // /mnt/share -o username=<machine_name>&lt;local_admin_username>,password=<local_admin_passoword>

Unfortunately there is no way to define explicitly the domain with the Docker for Windows so finally I entered my AD username without password and it started to work!

So I guess it could be fixed making the configuration more flexible.

(Ruloweb) #115

Had the same issue on Windows 10, I solved adding the Users users on the Sharing settings of D:

(Micnigh) #116

Thanks @ruloweb - that fixed it for me

(Megakoresh) #117

Make sure to allow the drive on which the folder is located through to the containers in the docker settings:
Docker tray > Settings > Shared drives > Tick the drive on which the folder is located.

(Vmeijer) #118

Changing unidentified networks to private fixed it for me. Is there a way to only apply this to the Docker network?

(Fernandolfs) #119

You´ve just saved my day, tks

(Atoa) #120

Thanks @ijeweb, this was very helpful. I ended up changing the specific interface to private instead of changing the ‘unidentified Networks’ policy. The following PowerShell command did it:

Set-NetConnectionProfile -InterfaceAlias "vEthernet (DockerNAT)" -NetworkCategory Private

I also ran into other issues so I wrote a shell script to manually mount the share:

(Swissgrammie) #121

where should I run this script? I have tried in a windows powershell and then in a privileged Ubuntu container