Docker Community Forums

Share and learn in the Docker community.

Cannot Share Drive in Windows 10


(Dvmrp) #1

Sorry to create a new thread even though it’s quite a popular issue in the forum. I’m using the Windows 10 insider build 15031. I tried to share the drive from the Docker’s setting. It does not work and return that firewall-related message. Then I opened the file explorer, typed “\\10.0.75.1” and error was returned after a while. It is the same even the Windows firewall is disabled. I used ‘net share’ on the command prompt and it did return the share folder, which is ‘d’ in my case.

I also tried to set the Docker virtual nic to’ Private’, restarted the docker, but it did not help the issue neither.

Docker version: 1.13.1

Any suggestion to continue the troubleshooting? Thanks.


Yet another thread for unable to share a drive in Windows 10
(Stephane Paul) #2

have you tried linking your drive using docker volume flag?

docker -v c:\hostpath:dockerpath


(Dvmrp) #3

Yes. it returns the message “C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: D: drive is not shared. Please share it in Docker for Windows Settings.”


(Reuwsaat) #4

On your tray, next to your clock, right-click on Docker, then click on Settings, there you’ll find the Shared Drives: just mark your drive and hit apply!


(Dvmrp) #5

Yes. that’s what I did and the issue I outlined in the first post. It said “Firewall Detected”. Here is the log,

[23:54:24.204][ApiProxy ][Info ] proxy << POST /v1.26/containers/4941f51f61ffec57c4497991650d982869b4275734c378580968b7cce29a8e44/start
[23:54:25.285][ApiProxy ][Info ] proxy << POST /v1.26/containers/4941f51f61ffec57c4497991650d982869b4275734c378580968b7cce29a8e44/attach?stderr=1&stdin=1&stdout=1&stream=1
[23:54:25.676][SambaShare ][Error ] Unable to mount D drive: firewall is blocking
[23:54:25.679][SambaShare ][Info ] Removing share D


(Reuwsaat) #6

My bad, I overlooked that!
I know that it isn’t exactly what you’re looking for, but try this and see if it works: move your project to C:/Users, edit the project folder’s permissions and add Full control to Users, then on your terminal, run docker run -p your_port:container_port -v /c/users/your_project:/your_container_workdir image_name command, make sure you’ve followed the Example section of this documentation.

I’ve been beating my head on this for days and just managed to get it working yesterday, though I did not have the firewall issue itself, my initial problem mas because I couldn’t get to share my E: drive, and was also having issues with the proper format of the path to share a volume with the container, and it also didn’t work with composer even though I used the same parameters on the docker run command I wrote above.


(Dvmrp) #7

I see. Yup. I did set the permission of the folder, tried ‘everyone’ and added full control. It still didn’t work. Also tried adding another share name, adding another user, nothing is related.


(Dvmrp) #8

While digging around, I found the following status info is a bit strange. The ip4connectivity is set to ‘NoTraffic’, not quite understand the implication.

Name : Unidentified network
InterfaceAlias : vEthernet (HNS Internal NIC)
InterfaceIndex : 32
NetworkCategory : Private
IPv4Connectivity : NoTraffic
IPv6Connectivity : NoTraffic

Name : Unidentified network
InterfaceAlias : vEthernet (DockerNAT) 2
InterfaceIndex : 11
NetworkCategory : Private
IPv4Connectivity : NoTraffic
IPv6Connectivity : NoTraffic


(Dvmrp) #9

I found the followings in the log. Apparently initially the share was created successfully, but later something failed and docker concluded that it’s a firewall issue.

[20:42:31.989][NamedPipeServer][Info ] Mount(D, JYUNG-SURFACEPR\jyung:**********, Docker.Core.Settings)
[20:42:31.989][SambaShare ][Info ] Mount D
[20:42:32.074][Cmd ][Info ] Share name D
[20:42:32.074][Cmd ][Info ] Path D:
[20:42:32.074][Cmd ][Info ] Remark
[20:42:32.074][Cmd ][Info ] Maximum users No limit
[20:42:32.077][Cmd ][Info ] Users
[20:42:32.077][Cmd ][Info ] Caching Manual caching of documents
[20:42:32.078][Cmd ][Info ] Permission Everyone, FULL
[20:42:32.078][Cmd ][Info ]
[20:42:32.078][Cmd ][Info ] The command completed successfully.
[20:42:32.078][Cmd ][Info ]
[20:42:32.087][SambaShare ][Info ] “D” is shared
[20:42:32.096][SambaShare ][Info ] Username: jyung
[20:42:32.096][SambaShare ][Info ] Host IP: 10.0.75.1
[20:42:32.096][SambaShare ][Info ] Cifs options: noperm,iocharset=utf8,nobrl,mfsymlinks,vers=3.02,domain=JYUNG-SURFACEPR




[20:42:32.748][ApiProxy ][Info ] Upgrading to raw stream
[20:42:32.750][ApiProxy ][Info ] proxy >> GET /v1.26/events?filters=%7B%22container%22%3A%7B%22b70848264c9c85063e38a6ef4067f674541fca9138acf863c01be2f3009e6837%22%3Atrue%7D%2C%22type%22%3A%7B%22container%22%3Atrue%7D%7D
[20:42:32.750][ApiProxy ][Info ] Dial Hyper-V socket f063fc15-ba59-4a54-8532-44f5a8bf4506:23a432c2-537a-4291-bcb5-d62504644739
[20:42:32.753][ApiProxy ][Info ] Successfully dialed Hyper-V socket f063fc15-ba59-4a54-8532-44f5a8bf4506:23a432c2-537a-4291-bcb5-d62504644739
[20:42:32.758][ApiProxy ][Info ] proxy >> POST /v1.26/containers/b70848264c9c85063e38a6ef4067f674541fca9138acf863c01be2f3009e6837/start [start]
[20:42:32.758][ApiProxy ][Info ] proxy >> POST /v1.26/containers/b70848264c9c85063e38a6ef4067f674541fca9138acf863c01be2f3009e6837/start
[20:42:32.758][ApiProxy ][Info ] Dial Hyper-V socket f063fc15-ba59-4a54-8532-44f5a8bf4506:23a432c2-537a-4291-bcb5-d62504644739
[20:42:32.759][ApiProxy ][Info ] Successfully dialed Hyper-V socket f063fc15-ba59-4a54-8532-44f5a8bf4506:23a432c2-537a-4291-bcb5-d62504644739
[20:42:33.188][ApiProxy ][Info ] proxy << POST /v1.26/containers/b70848264c9c85063e38a6ef4067f674541fca9138acf863c01be2f3009e6837/start
[20:42:34.271][ApiProxy ][Info ] proxy << POST /v1.26/containers/b70848264c9c85063e38a6ef4067f674541fca9138acf863c01be2f3009e6837/attach?stderr=1&stdin=1&stdout=1&stream=1
[20:42:34.760][ApiProxy ][Info ] Cancel connection…
[20:42:34.764][ApiProxy ][Info ] proxy << GET /v1.26/events?filters=%7B%22container%22%3A%7B%22b70848264c9c85063e38a6ef4067f674541fca9138acf863c01be2f3009e6837%22%3Atrue%7D%2C%22type%22%3A%7B%22container%22%3Atrue%7D%7D
[20:42:34.778][SambaShare ][Error ] Unable to mount D drive: firewall is blocking
[20:42:34.778][SambaShare ][Info ] Removing share D
[20:42:34.847][NamedPipeClient][Info ] Received response for Mount
[20:42:34.846][NamedPipeServer][Info ] Mount done in 00:00:02.8575207.


(Artisticcheese) #10

Are you trying to access running docker container file system remotely over file sharing? I’m confused about your setup.


(Dvmrp) #11

Hi all, the latest Windows 10 insider build 15042 fixed it. Thanks for looking into it.


(Dvmrp) #12

It does not work now. Another observation is that after the share attempt failed, the share drive became ‘disabled’.

Turning off the firewall does not help. So it’s probably not a firewall issue.

Windows 10 Pro 1703
Docker 17.03.1


(Dvmrp) #13

Open file explorer and type

  1. //127.0.0.1 or //local interface address --> the shared drive can be accessed
  2. //10.0.75.1 --> Windows cannot access 10.0.75.1
  3. //172.26.96.1 (another vEthernet NIC that is assigned into public network) --> the shared drive can be accessed

I checked the sharing option for both private and public network and both are enabled.

(Firewall log is enabled and no blocking is recorded for 10.0.75.x)

What may be the possible reasons for the inaccessbility to docker vEthernet NIC?


(Dvmrp) #14

Just upgraded docker and the issue is fixed. The reason seems to be documented in the release note.


(Lewandpdnm) #15

What is the version that you updated Docker to that worked; I am having the same issue?