Cannot share drive

[acojocaru]

Expected behavior

C drive is shared.

Actual behavior

C drive is not shared.

Information

Diagnostic ID: 91D661A3-3A6B-487F-B357-51E1F1779C0E/2017-12-07_18-48-32
Docker version: 17.09.0-ce-win33 (13620)
Windows version: 10 Pro N, version 1709

Steps to reproduce the behavior

1. Select the C drive from Shared Drives and click on Apply.
2. Enter the username and password and then click OK.
   Result: C drive is not shared.

Here's the relevant part from the log file:

[18:45:08.943][SambaShare     ][Info   ] Creating share "C:\" as "C" with Full Control to "Alexandru"
[18:45:09.057][Cmd            ][Info   ] C was shared successfully.
[18:45:09.099][Cmd            ][Info   ] Share name        C
[18:45:09.100][Cmd            ][Info   ] Path              C:\
[18:45:09.100][Cmd            ][Info   ] Remark            
[18:45:09.100][Cmd            ][Info   ] Maximum users     No limit
[18:45:09.100][Cmd            ][Info   ] Users             
[18:45:09.100][Cmd            ][Info   ] Caching           Caching disabled
[18:45:09.100][Cmd            ][Info   ] Permission        DESKTOP-9N7R2H9\Alexandru, FULL
[18:45:09.100][Cmd            ][Info   ] The command completed successfully.
[18:45:09.104][SambaShare     ][Info   ] "C" is shared
[18:45:09.106][SambaShare     ][Info   ] Username: Alexandru
[18:45:09.106][SambaShare     ][Info   ] Host IP: 10.0.75.1
[18:45:09.106][SambaShare     ][Info   ] Cifs options: noperm,iocharset=utf8,nobrl,mfsymlinks,vers=3.02,domain=DESKTOP-9N7R2H9
[18:45:09.174][ApiProxy       ][Info   ] proxy >> GET /_ping
[18:45:09.174][ApiProxy       ][Info   ] Dial Hyper-V socket 9253e036-f704-472b-abce-7c738c71831c:23a432c2-537a-4291-bcb5-d62504644739
[18:45:09.176][ApiProxy       ][Info   ] Successfully dialed Hyper-V socket 9253e036-f704-472b-abce-7c738c71831c:23a432c2-537a-4291-bcb5-d62504644739
[18:45:09.176][ApiProxy       ][Info   ] proxy << GET /_ping
[18:45:09.177][ApiProxy       ][Info   ] proxy >> POST /v1.32/images/load?quiet=1
[18:45:09.177][ApiProxy       ][Info   ] Dial Hyper-V socket 9253e036-f704-472b-abce-7c738c71831c:23a432c2-537a-4291-bcb5-d62504644739
[18:45:09.178][ApiProxy       ][Info   ] Successfully dialed Hyper-V socket 9253e036-f704-472b-abce-7c738c71831c:23a432c2-537a-4291-bcb5-d62504644739
[18:45:09.294][ApiProxy       ][Info   ] proxy << POST /v1.32/images/load?quiet=1
[18:45:09.368][ApiProxy       ][Info   ] proxy >> GET /_ping
[18:45:09.368][ApiProxy       ][Info   ] Dial Hyper-V socket 9253e036-f704-472b-abce-7c738c71831c:23a432c2-537a-4291-bcb5-d62504644739
[18:45:09.369][ApiProxy       ][Info   ] Successfully dialed Hyper-V socket 9253e036-f704-472b-abce-7c738c71831c:23a432c2-537a-4291-bcb5-d62504644739
[18:45:09.370][ApiProxy       ][Info   ] proxy << GET /_ping
[18:45:09.375][ApiProxy       ][Info   ] proxy >> POST /v1.32/containers/create [rewriteBinds]
[18:45:09.389][ApiProxy       ][Info   ] Failed to read proxies/http from snaphshot p9p.MessageRerror{Ename:"No such file or directory"}
[18:45:09.389][ApiProxy       ][Info   ] proxy >> POST /v1.32/containers/create
[18:45:09.389][ApiProxy       ][Info   ] Dial Hyper-V socket 9253e036-f704-472b-abce-7c738c71831c:23a432c2-537a-4291-bcb5-d62504644739
[18:45:09.390][ApiProxy       ][Info   ] Successfully dialed Hyper-V socket 9253e036-f704-472b-abce-7c738c71831c:23a432c2-537a-4291-bcb5-d62504644739
[18:45:09.392][ApiProxy       ][Info   ] proxy << POST /v1.32/containers/create
[18:45:09.397][SambaShare     ][Error  ] Unable to mount C drive: C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: error creating overlay mount to /var/lib/docker/overlay2/9e58336311d318ab606bdbdd6f79e6f1d5ef6498e25fa3ac66fef629c42785b2-init/merged: no such file or directory.
See 'C:\Program Files\Docker\Docker\Resources\bin\docker.exe run --help'.

[18:45:09.397][SambaShare     ][Info   ] Removing share C
[18:45:09.439][NamedPipeClient][Info   ] Received response for Mount
[18:45:09.439][NamedPipeServer][Info   ] Mount done in 00:00:01.2299185.

I have also tried disabling my firewall and re-installing Docker, but I'm still getting the same error.

[DBosley]

Having the exact same issues. Brand new install of docker, no custom configurations.

[colthreepv]

This is really a common disease, I am using docker 4 windows from months, and at every reboot I have to do this

There are many issues covering this problem, one (long-term) solution, is the new LCOW support in edge releases
It does not work anymore with "shared drives", it just has access to the disks, as it works on a lower-level (AFAIK)

For now LCOW has limitations (no multi-stage & others) as you can see in the Issues, but the "firewall" problem is going away in some month, finally

[acojocaru]

Thanks for the information, @colthreepv. Let's hope this gets fixed in 17.12. Right now, this makes Docker for Windows extremely limited for me.

[Mr-Black-Dahlia]

This is really making me upset. First time using docker and I cant... WTF Why would I ever pay for this?

EDIT: I was able to turn off windows firewall specifically for the DockerNAT. I did this within WINDOWS DEFENDER.

THIS fixed my issue and I am able to connect. You can leave windows firewall on for your regular Ethernet connection, but turn it off for the dockernat. Once I did this it worked fine.

EVEN THOUGH it was allowed in windows firewall.

TLDR:

Disable the firewall for the DOCKER NAT inside WINDOWS DEFENDER.

[vokamut]

I set the password for the current user and it worked

[Naramsim]

@indiecore-fm Did you pay for Docker CE?

[docker-robott]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked