Volume not writable in windows about for-win HOT 18 CLOSED

moved to 1.12.0-stable (build 5968) and now I dont even get access to the directory

[09:55:59.854][SambaShare ][Info ] "C" is shared
[09:55:59.859][SambaShare ][Info ] Challenging credentials with host
[09:55:59.927][SambaShare ][Info ] Challenging credentials with host succeeded
[09:55:59.938][NamedPipeClient][Info ] Received response for TryShare
[09:55:59.933][NamedPipeServer][Info ] TryShare done.
[09:55:59.946][NamedPipeClient][Info ] Sending Mount(C, [email protected]:_)...
[09:55:59.954][NamedPipeServer][Info ] Mount(C, [email protected]:_)
[09:55:59.959][HyperV ][Info ] Mount C
[09:56:06.105][NamedPipeClient][Info ] Received response for Mount
[09:56:06.109][NamedPipeClient][Info ] Sending Unmount(D)...
[09:56:06.100][NamedPipeServer][Info ] Mount done.
[09:56:06.113][NamedPipeServer][Info ] Unmount(D)
[09:56:06.119][HyperV ][Info ] Unmount D
[09:56:10.173][NamedPipeClient][Info ] Received response for Unmount
[09:56:10.167][NamedPipeServer][Info ] Unmount done.
[09:56:13.051][ApiProxy ][Info ] proxy >> POST /v1.24/containers/create [rewriteBinds]
[09:56:13.058][ApiProxy ][Info ] Rewrote mount c:/Users:/data (volumeDriver=) to /c/Users:/data
[09:56:13.075][ApiProxy ][Info ] Failed to Walk to [snapshots 5d5e643261b549d006129dbf9ff0ba8ac6e604b1 ro com.docker.driver.amd64-linux proxy http] 9p: No such file or directory
[09:56:13.084][ApiProxy ][Info ] Failed to read proxies/http from snaphshot p9p.MessageRerror{Ename:"No such file or directory"}

from for-win.

Thanks for the reports. We discovered an issue with how we handle passwords and some passwords with some non alphanumeric characters won't work (examples characters are ;, ", ,, *). If your password contained some of these, the sharing may not work.

Do you have some of these special characters in your password?

We do have a fix for this and will push it out on the beta channel as Beta22 very soon (hopefully later today). It would be great if you could test it then.

from for-win.

The fixed was pushed earlier, please give it a try: https://download.docker.com/win/beta/1.12.0.6313/NOTES

from for-win.

well the release notes are there but even when i uninstall docker and then
reinstall from the download beta i still get the beta21 version.

On Thu, Aug 11, 2016 at 6:44 PM, Michael Friis [email protected]
wrote:

The fixed was pushed earlier, please give it a try:
https://download.docker.com/win/beta/1.12.0.6313/NOTES

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#32 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AB9NHZXx6_cBZlZeQsx9fX7hiMEUZX2Hks5qe1FugaJpZM4Jg2i7
.

Graham Cunningham
Tel : +41 26 401 4049

from for-win.

@swissgrammie unfortunately we had to pull the release last minute as we discovered an issue with the auto-update. This issue is now fixed and we are planning another beta release early next week. Apologies for the delay

from for-win.

The beta is now out and downloadable from https://download.docker.com/win/beta/InstallDocker.msi

It would great if you could try it and let us know if it fixed your issue.

Thanks
Rolf

from for-win.

Hi,

just tried it, clean install with a reboot in between, no change, still
problems with accessing the volumes. I tried creating a local admin user
"docker" with an 8 character password and the same problem.
docker run --rm -v c:/Users:/data alpine ls /data

simply returns, nothing is displayed. The windows user i am using is an
admin. and if i change the run command slightly
docker run --rm -v c:/:/data alpine ls /data

I get
Users

tried a few combinations of //C etc etc but nothing works. reset
credentials a couple of times as well.

I am on the windows insider preview, current version which is Version 1607
(Build OS 14901.1000)

regards
graham

On Wed, Aug 17, 2016 at 1:21 PM, Rolf Neugebauer [email protected]
wrote:

The beta is now out and downloadable from https://download.docker.com/
win/beta/InstallDocker.msi

It would great if you could try it and let us know if it fixed your issue.

Thanks
Rolf

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#32 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AB9NHV0d2ZD1jw463vJIZcNExrszFHF9ks5qgu66gaJpZM4Jg2i7
.

Graham Cunningham
Tel : +41 26 401 4049

from for-win.

@swissgrammie thanks for getting back to us so quickly. Could you got to Diagnostics & Feedback and upload a diagnostics report for us to take a look at? We'd need the diagnostics ID printed out.
thanks
rolf

from for-win.

3086D4E4-A0C7-4566-B101-2EEB1A64DA21/2016-08-17_15-57-46

On Wed, Aug 17, 2016 at 3:24 PM, Rolf Neugebauer [email protected]
wrote:

@swissgrammie https://github.com/swissgrammie thanks for getting back
to us so quickly. Could you got to Diagnostics & Feedback and upload a
diagnostics report for us to take a look at? We'd need the diagnostics ID
printed out.
thanks
rolf

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#32 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AB9NHYxM7QW80MIHhkxPpGVnV0sgJ0BYks5qgwuAgaJpZM4Jg2i7
.

Graham Cunningham
Tel : +41 26 401 4049

from for-win.

Hi Graham,
thanks again for the quick response. I took a look at the logs. The shared drive is not mounted inside the Linux VM. The mount failed with:

Aug 17 13:56:40 moby user.info KVP: mount: cifs //10.0.75.1/C to /C and /c
Aug 17 13:56:49 moby user.err KVP: mount: error: 20 Not a directory
Aug 17 13:56:50 moby kern.err kernel: CIFS VFS: Error connecting to socket. Aborting operation.
Aug 17 13:56:50 moby kern.err kernel: CIFS VFS: cifs_mount failed w/return code = -115

I'm not entirely sure what that error is, but I noticed something else in the logs, which might help. If you do a net share C, from the logs it looks like it is shared with two users (Administrator and Graham). This could be the source of the issue...

Could you:

1. Reset Credentials in the Shared Drive Settings menu.
2. In an elevated shell execute net share C /delete and verify with net share C that the share does not exist anymore.
3. Share the C drive again, enter your credentials and then try again
   Thanks
   Rolf

from for-win.

[19:48:39.300][SambaShare     ][Info   ] "C" is not shared
[19:48:39.305][SambaShare     ][Info   ] Creating share "C:\" as "C" with Full Control to "ken"
[19:48:39.367][Cmd            ][Info   ] C was shared successfully.
[19:48:39.372][Cmd            ][Info   ] 
[19:48:39.398][Cmd            ][Info   ] Share name        C
[19:48:39.402][Cmd            ][Info   ] Path              C:\
[19:48:39.405][Cmd            ][Info   ] Remark            
[19:48:39.408][Cmd            ][Info   ] Maximum users     No limit
[19:48:39.411][Cmd            ][Info   ] Users             
[19:48:39.414][Cmd            ][Info   ] Caching           Caching disabled
[19:48:39.418][Cmd            ][Info   ] Permission        KEN-PC\ken, FULL
[19:48:39.421][Cmd            ][Info   ] 
[19:48:39.424][Cmd            ][Info   ] The command completed successfully.
[19:48:39.427][Cmd            ][Info   ] 
[19:48:39.430][SambaShare     ][Info   ] "C" is shared
[19:48:39.434][SambaShare     ][Info   ] Challenging credentials with host
[19:48:39.492][SambaShare     ][Info   ] Challenging credentials with host succeeded
[19:48:39.499][NamedPipeClient][Info   ] Received response for TryShare
[19:48:39.504][NamedPipeClient][Info   ] Sending Mount(C, ken:**********)...
[19:48:39.495][NamedPipeServer][Info   ] TryShare done.
[19:48:39.509][NamedPipeServer][Info   ] Mount(C, ken:**********)
[19:48:39.512][HyperV         ][Info   ] Mount C
[19:48:45.589][NamedPipeClient][Info   ] Received response for Mount
[19:48:45.599][NamedPipeClient][Info   ] Sending Unmount(D)...
[19:48:45.579][NamedPipeServer][Info   ] Mount done.
[19:48:45.611][NamedPipeServer][Info   ] Unmount(D)
[19:48:45.620][HyperV         ][Info   ] Unmount D
[19:48:49.620][NamedPipeClient][Info   ] Received response for Unmount
[19:48:49.609][NamedPipeServer][Info   ] Unmount done.
[19:49:11.832][FeedbackSettings][Info   ] Open logs

8EE7D739-03B1-4BC2-ADE6-C43ACFCF34AF/2016-08-28_19-51-55

Shared directory still appear empty. Already tried, latest beta and stable.

from for-win.

+1 Same problem here.
Can I provide extra info?

from for-win.

Seems working again in insider build 14915

from for-win.

@Kurdym sorry, missed your comment. can you provide a diagnostics ID for me to take a look at?

from for-win.

@swissgrammie do you still have the issue? If so, it could be related to firewall settings. Could you try what I suggest here.
thanks
rolf

from for-win.

Hi Rolf,

So I had a workaround, which was whenever i changed networks, I had to
delete my share, recreate the share, grant myself full access and then
restart docker, i did this with a script. With the last windows update on
Friday however this all seems to work fine without recreating the share

regards
graham

On Tue, Sep 6, 2016 at 12:10 PM Rolf Neugebauer [email protected]
wrote:

@swissgrammie https://github.com/swissgrammie do you still have the
issue? If so, it could be related to firewall settings. Could you try what
I suggest here
#25 (comment).
thanks

rolf

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#32 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AB9NHQ-hPFkUAbJAXIY1SeArmJphyqpMks5qnTv7gaJpZM4Jg2i7
.

from for-win.

@swissgrammie glad to hear it works for you now.

I'm closing this issue. if you still have issues after trying:

• use the Beta channel (https://download.docker.com/win/beta/InstallDocker.msi)
• domain users should use domain\username
• if you have multiple users, make sure the share is done with your user (net share c) and not a different one. you can delete shares with net share c /delete
  please head over to #25 and provide details there.

from for-win.

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

from for-win.