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

Can't share drive on domain account #313

Closed
totomakers opened this Issue Dec 12, 2016 · 11 comments

Comments

Projects
None yet
6 participants
@totomakers

totomakers commented Dec 12, 2016

Expected behavior

Share C:/ drive from Docker

Actual behavior

Nothing happend.

Information

[09:22:31.492][SambaShare     ][Info   ] Removing share C
[09:22:31.520][Moby           ][Info   ] 2016/12/12 09:22:30 46 error CloseRead on vsock: HvSocket has been closed for read
[09:22:31.537][SambaShare     ][Info   ] Mount C
[09:22:31.547][Moby           ][Info   ] 2016/12/12 09:22:30 46 Done. read: 252 written: 1256
[09:22:31.574][Cmd            ][Info   ] Cette ressource partag‚e n'existe pas.
[09:22:31.574][Cmd            ][Info   ] 
[09:22:31.574][Cmd            ][Info   ] Vous obtiendrez une aide suppl‚mentaire en entrant NET HELPMSG 2310.
[09:22:31.574][Cmd            ][Info   ] 
[09:22:31.578][SambaShare     ][Info   ] "C" is not shared
[09:22:31.578][SambaShare     ][Info   ] Creating share "C:\" as "C" with Full Control to "xxxx"
[09:22:31.660][Cmd            ][Info   ] C a ‚t‚ partag‚.
[09:22:31.660][Cmd            ][Info   ] 
[09:22:31.704][Cmd            ][Info   ] Nom du partage            C
[09:22:31.704][Cmd            ][Info   ] Chemin d'accŠsÿ:          C:\
[09:22:31.704][Cmd            ][Info   ] Remarque                  
[09:22:31.704][Cmd            ][Info   ] Max. Utils.               Pas de limite
[09:22:31.704][Cmd            ][Info   ] Utilisateurs              
[09:22:31.704][Cmd            ][Info   ] Mise en cache             Mise en cache d‚sactiv‚e
[09:22:31.705][Cmd            ][Info   ] Autorisation              PO057\xxxx, FULL
[09:22:31.705][Cmd            ][Info   ] 
[09:22:31.705][Cmd            ][Info   ] La commande s'est termin‚e correctement.
[09:22:31.705][Cmd            ][Info   ] 
[09:22:31.709][SambaShare     ][Info   ] "C" is shared
[09:22:31.712][SambaShare     ][Info   ] Username: xxxx
[09:22:31.712][SambaShare     ][Info   ] Host IP: 10.0.75.1
[09:22:31.712][SambaShare     ][Info   ] Cifs options: noperm,iocharset=utf8,nobrl,mfsymlinks,vers=3.02,domain=PO057
[09:22:31.772][ApiProxy       ][Info   ] proxy >> GET /_ping
[09:22:31.772][ApiProxy       ][Info   ] Dial Hyper-V socket 2e0b7396-5101-4438-9eac-ca4c148608e5:23a432c2-537a-4291-bcb5-d62504644739
[09:22:31.772][ApiProxy       ][Info   ] Successfully dialed Hyper-V socket 2e0b7396-5101-4438-9eac-ca4c148608e5:23a432c2-537a-4291-bcb5-d62504644739
[09:22:31.783][Moby           ][Info   ] 2016/12/12 09:22:30 Connection 47 to: 23a432c2-537a-4291-bcb5-d62504644739 from: 00000000-0000-0000-0000-000000000000:49571334-be23-11e6-9bd3-e02a82d27371
[09:22:31.788][ApiProxy       ][Info   ] proxy << GET /_ping
[09:22:31.789][ApiProxy       ][Info   ] proxy >> POST /v1.25/images/load?quiet=1
[09:22:31.789][ApiProxy       ][Info   ] Dial Hyper-V socket 2e0b7396-5101-4438-9eac-ca4c148608e5:23a432c2-537a-4291-bcb5-d62504644739
[09:22:31.809][Moby           ][Info   ] 2016/12/12 09:22:30 47 error copying from vsock to docker: read hvsock:10: bad file descriptor
[09:22:31.812][ApiProxy       ][Info   ] Successfully dialed Hyper-V socket 2e0b7396-5101-4438-9eac-ca4c148608e5:23a432c2-537a-4291-bcb5-d62504644739
[09:22:31.826][Moby           ][Info   ] 2016/12/12 09:22:30 47 error CloseRead on vsock: HvSocket has been closed for read
[09:22:31.838][Moby           ][Info   ] 2016/12/12 09:22:30 Connection 48 to: 23a432c2-537a-4291-bcb5-d62504644739 from: 00000000-0000-0000-0000-000000000000:49571335-be23-11e6-9bd3-e02a82d27371
[09:22:31.846][Moby           ][Info   ] 2016/12/12 09:22:30 47 error CloseWrite on vsock: HvSocket has been closed for write
[09:22:31.850][Moby           ][Info   ] 2016/12/12 09:22:30 47 Done. read: 85 written: 199
[09:22:31.977][ApiProxy       ][Info   ] proxy << POST /v1.25/images/load?quiet=1
[09:22:32.006][Moby           ][Info   ] 2016/12/12 09:22:30 48 error copying from vsock to docker: read hvsock:4: bad file descriptor
[09:22:32.030][Moby           ][Info   ] 2016/12/12 09:22:30 48 error CloseWrite on vsock: HvSocket has been closed for write
[09:22:32.037][Moby           ][Info   ] 2016/12/12 09:22:30 48 error CloseRead on vsock: HvSocket has been closed for read
[09:22:32.042][Moby           ][Info   ] 2016/12/12 09:22:30 48 Done. read: 96457 written: 257
[09:22:32.045][ApiProxy       ][Info   ] proxy >> GET /_ping
[09:22:32.045][ApiProxy       ][Info   ] Dial Hyper-V socket 2e0b7396-5101-4438-9eac-ca4c148608e5:23a432c2-537a-4291-bcb5-d62504644739
[09:22:32.050][ApiProxy       ][Info   ] Successfully dialed Hyper-V socket 2e0b7396-5101-4438-9eac-ca4c148608e5:23a432c2-537a-4291-bcb5-d62504644739
[09:22:32.060][Moby           ][Info   ] 2016/12/12 09:22:30 Connection 49 to: 23a432c2-537a-4291-bcb5-d62504644739 from: 00000000-0000-0000-0000-000000000000:4957133a-be23-11e6-9bd3-e02a82d27371
[09:22:32.064][ApiProxy       ][Info   ] proxy << GET /_ping
[09:22:32.067][ApiProxy       ][Info   ] proxy >> POST /v1.25/containers/create [rewriteBinds]
[09:22:32.081][Moby           ][Info   ] 2016/12/12 09:22:30 49 error copying from vsock to docker: read hvsock:6: bad file descriptor
[09:22:32.083][ApiProxy       ][Info   ] Failed to Walk to [snapshots ab4fe93ddbf84ce4148d4b7380f16d39a585e0ae ro com.docker.driver.amd64-linux proxy http] 9p: No such file or directory
[09:22:32.085][ApiProxy       ][Info   ] Failed to read proxies/http from snaphshot p9p.MessageRerror{Ename:"No such file or directory"}
[09:22:32.085][ApiProxy       ][Info   ] proxy >> POST /v1.25/containers/create
[09:22:32.085][ApiProxy       ][Info   ] Dial Hyper-V socket 2e0b7396-5101-4438-9eac-ca4c148608e5:23a432c2-537a-4291-bcb5-d62504644739
[09:22:32.091][ApiProxy       ][Info   ] Successfully dialed Hyper-V socket 2e0b7396-5101-4438-9eac-ca4c148608e5:23a432c2-537a-4291-bcb5-d62504644739
[09:22:32.100][Moby           ][Info   ] 2016/12/12 09:22:30 49 error CloseWrite on vsock: HvSocket has been closed for write
[09:22:32.110][Moby           ][Info   ] 2016/12/12 09:22:30 49 error CloseRead on vsock: HvSocket has been closed for read
[09:22:32.113][Moby           ][Info   ] 2016/12/12 09:22:30 49 Done. read: 85 written: 199
[09:22:32.120][Moby           ][Info   ] 2016/12/12 09:22:30 Connection 50 to: 23a432c2-537a-4291-bcb5-d62504644739 from: 00000000-0000-0000-0000-000000000000:4957133b-be23-11e6-9bd3-e02a82d27371
[09:22:32.216][ApiProxy       ][Info   ] proxy << POST /v1.25/containers/create
[09:22:32.238][Moby           ][Info   ] 2016/12/12 09:22:30 50 error copying from vsock to docker: read hvsock:5: bad file descriptor
[09:22:32.243][ApiProxy       ][Info   ] proxy >> POST /v1.25/containers/ea9785b2b81d3e02b74046fb54cf2e073f69436f383c18653440966a0e4b0b45/attach?stderr=1&stdin=1&stdout=1&stream=1
[09:22:32.243][ApiProxy       ][Info   ] Dial Hyper-V socket 2e0b7396-5101-4438-9eac-ca4c148608e5:23a432c2-537a-4291-bcb5-d62504644739
[09:22:32.258][Moby           ][Info   ] 2016/12/12 09:22:30 50 error CloseWrite on vsock: HvSocket has been closed for write
[09:22:32.271][Moby           ][Info   ] 2016/12/12 09:22:30 50 error CloseRead on vsock: HvSocket has been closed for read
[09:22:32.279][Moby           ][Info   ] 2016/12/12 09:22:30 50 Done. read: 2126 written: 284
[09:22:32.283][ApiProxy       ][Info   ] Successfully dialed Hyper-V socket 2e0b7396-5101-4438-9eac-ca4c148608e5:23a432c2-537a-4291-bcb5-d62504644739
[09:22:32.298][Moby           ][Info   ] 2016/12/12 09:22:30 Connection 51 to: 23a432c2-537a-4291-bcb5-d62504644739 from: 00000000-0000-0000-0000-000000000000:4957133c-be23-11e6-9bd3-e02a82d27371
[09:22:32.301][ApiProxy       ][Info   ] Upgrading to raw stream
[09:22:32.302][ApiProxy       ][Info   ] proxy >> POST /v1.25/containers/ea9785b2b81d3e02b74046fb54cf2e073f69436f383c18653440966a0e4b0b45/start [start]
[09:22:32.302][ApiProxy       ][Info   ] proxy >> POST /v1.25/containers/ea9785b2b81d3e02b74046fb54cf2e073f69436f383c18653440966a0e4b0b45/start
[09:22:32.302][ApiProxy       ][Info   ] Dial Hyper-V socket 2e0b7396-5101-4438-9eac-ca4c148608e5:23a432c2-537a-4291-bcb5-d62504644739
[09:22:32.304][ApiProxy       ][Info   ] proxy >> GET /v1.25/events?filters=%7B%22container%22%3A%7B%22ea9785b2b81d3e02b74046fb54cf2e073f69436f383c18653440966a0e4b0b45%22%3Atrue%7D%2C%22type%22%3A%7B%22container%22%3Atrue%7D%7D
[09:22:32.304][ApiProxy       ][Info   ] Dial Hyper-V socket 2e0b7396-5101-4438-9eac-ca4c148608e5:23a432c2-537a-4291-bcb5-d62504644739
[09:22:32.319][Moby           ][Info   ] 2016/12/12 09:22:30 51 error CloseRead on vsock: HvSocket has been closed for read
[09:22:32.324][ApiProxy       ][Info   ] Successfully dialed Hyper-V socket 2e0b7396-5101-4438-9eac-ca4c148608e5:23a432c2-537a-4291-bcb5-d62504644739
[09:22:32.332][Moby           ][Info   ] 2016/12/12 09:22:30 Connection 52 to: 23a432c2-537a-4291-bcb5-d62504644739 from: 00000000-0000-0000-0000-000000000000:4957133d-be23-11e6-9bd3-e02a82d27371
[09:22:32.337][ApiProxy       ][Info   ] Successfully dialed Hyper-V socket 2e0b7396-5101-4438-9eac-ca4c148608e5:23a432c2-537a-4291-bcb5-d62504644739
[09:22:32.347][Moby           ][Info   ] 2016/12/12 09:22:30 Connection 53 to: 23a432c2-537a-4291-bcb5-d62504644739 from: 00000000-0000-0000-0000-000000000000:4957133e-be23-11e6-9bd3-e02a82d27371
[09:22:32.687][ApiProxy       ][Info   ] proxy << POST /v1.25/containers/ea9785b2b81d3e02b74046fb54cf2e073f69436f383c18653440966a0e4b0b45/start
[09:22:32.708][Moby           ][Info   ] 2016/12/12 09:22:31 53 error copying from vsock to docker: read hvsock:8: bad file descriptor
[09:22:32.744][Moby           ][Info   ] 2016/12/12 09:22:31 53 error CloseRead on vsock: HvSocket has been closed for read
[09:22:32.759][Moby           ][Info   ] 2016/12/12 09:22:31 53 error CloseWrite on vsock: HvSocket has been closed for write
[09:22:32.765][Moby           ][Info   ] 2016/12/12 09:22:31 53 Done. read: 213 written: 145
[09:22:32.857][ApiProxy       ][Info   ] proxy << POST /v1.25/containers/ea9785b2b81d3e02b74046fb54cf2e073f69436f383c18653440966a0e4b0b45/attach?stderr=1&stdin=1&stdout=1&stream=1
[09:22:32.863][Moby           ][Info   ] 2016/12/12 09:22:31 51 Done. read: 283 written: 317
[09:22:33.274][ApiProxy       ][Info   ] Cancel connection...
[09:22:33.284][SambaShare     ][Error  ] Unable to mount C drive: 10.0.75.1 (10.0.75.1:445) open
mount error(112): Host is down
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
mount: mounting //10.0.75.1/C on /c failed: Invalid argument

[09:22:33.284][SambaShare     ][Info   ] Removing share C
[09:22:33.309][Moby           ][Info   ] 2016/12/12 09:22:31 52 error CloseRead on vsock: HvSocket has been closed for read
[09:22:33.315][ApiProxy       ][Info   ] proxy << GET /v1.25/events?filters=%7B%22container%22%3A%7B%22ea9785b2b81d3e02b74046fb54cf2e073f69436f383c18653440966a0e4b0b45%22%3Atrue%7D%2C%22type%22%3A%7B%22container%22%3Atrue%7D%7D
[09:22:33.328][Moby           ][Info   ] 2016/12/12 09:22:31 52 Done. read: 252 written: 1265
[09:22:33.341][NamedPipeClient][Info   ] Received response for Mount
[09:22:33.340][NamedPipeServer][Info   ] Mount done in 00:00:04.0380539.
[09:22:33.357][SegmentApi     ][Info   ] Usage statistic: actionSettingsChanged
[09:22:35.972][FeedbackSettings][Info   ] Open logs`
Client:
 Version:      1.13.0-rc3
 API version:  1.25
 Go version:   go1.7.3
 Git commit:   4d92237
 Built:        Tue Dec  6 01:15:44 2016
 OS/Arch:      windows/amd64

Server:
 Version:      1.13.0-rc3
 API version:  1.25 (minimum version 1.12)
 Go version:   go1.7.3
 Git commit:   4d92237
 Built:        Tue Dec  6 01:15:44 2016
 OS/Arch:      linux/amd64
 Experimental: true

Steps to reproduce the behavior

  1. Login in DOMAIN/ACCOUNT
  2. Run docker and try share drive
  3. Nothing happen and drive is not share

What i try

  1. Create share on windows and type //10.0.75.1/ on explorer : Share is create
  2. Try to ping 10.0.75.1 and my machine from MobyLinuxVM : Works
  3. Try the cmd for mounting the share drive, fail : "No such file or directory..."

Thanks for help :)

@simonferquel

This comment has been minimized.

Show comment
Hide comment
@simonferquel

simonferquel Dec 12, 2016

Hi,
Could you send a diagnostic just after trying to share the C drive ?

Is there a 3rd party firewall on your machine ?

simonferquel commented Dec 12, 2016

Hi,
Could you send a diagnostic just after trying to share the C drive ?

Is there a 3rd party firewall on your machine ?

@totomakers

This comment has been minimized.

Show comment
Hide comment
@totomakers

totomakers Dec 12, 2016

Diagnostic ID : 6B0AB737-1E6B-4FCD-9CE0-ABFE66987E4B/2016-12-12_11-53-06

It's clean install of windows, firewall disabled and windows defender too :)

totomakers commented Dec 12, 2016

Diagnostic ID : 6B0AB737-1E6B-4FCD-9CE0-ABFE66987E4B/2016-12-12_11-53-06

It's clean install of windows, firewall disabled and windows defender too :)

@simonferquel

This comment has been minimized.

Show comment
Hide comment
@simonferquel

simonferquel Dec 12, 2016

Is this an on premise Domain or an Azure AD domain ?

simonferquel commented Dec 12, 2016

Is this an on premise Domain or an Azure AD domain ?

@totomakers

This comment has been minimized.

Show comment
Hide comment
@totomakers

totomakers Dec 12, 2016

Not an Azure AD domain :)

totomakers commented Dec 12, 2016

Not an Azure AD domain :)

@simonferquel

This comment has been minimized.

Show comment
Hide comment
@simonferquel

simonferquel Dec 12, 2016

Ok, so is the AD controllable reachable from your computer while testing ?

simonferquel commented Dec 12, 2016

Ok, so is the AD controllable reachable from your computer while testing ?

@totomakers

This comment has been minimized.

Show comment
Hide comment
@totomakers

totomakers Dec 12, 2016

I didn't know how my compagny manage the domain. But i can ask them. What should i do ?

totomakers commented Dec 12, 2016

I didn't know how my compagny manage the domain. But i can ask them. What should i do ?

@simonferquel

This comment has been minimized.

Show comment
Hide comment
@simonferquel

simonferquel Dec 12, 2016

If your on your corporate network, it should be good.
From the diags, I see that smb2/smb3 are disabled (maybe due to a corporate policy). Could you ask your administrator if there is a policy blocking file sharing in your network ? (we rely on Samba file sharing in Docker for Windows)

simonferquel commented Dec 12, 2016

If your on your corporate network, it should be good.
From the diags, I see that smb2/smb3 are disabled (maybe due to a corporate policy). Could you ask your administrator if there is a policy blocking file sharing in your network ? (we rely on Samba file sharing in Docker for Windows)

@totomakers

This comment has been minimized.

Show comment
Hide comment
@totomakers

totomakers Dec 12, 2016

Ah ! it's solve my issue.

regedit -> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
Set SMB2 Key to 1 (enabled)

Thanks for help 👍

totomakers commented Dec 12, 2016

Ah ! it's solve my issue.

regedit -> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
Set SMB2 Key to 1 (enabled)

Thanks for help 👍

@pmcdowell-okta

This comment has been minimized.

Show comment
Hide comment
@pmcdowell-okta

pmcdowell-okta May 15, 2017

I tried everything to resolve this (except the last solution, too late now), my solution was to put my shiny new Lenovo Laptop on Craigslist, sell it, and buy a Macbook Pro.

I hope someone from Microsoft is seeing this, Windows 10 is bad. I don't think this is a docker problem as much as a Microsoft problem, they seemed to have changed something in windows 10 that makes the shares not work as they should.

pmcdowell-okta commented May 15, 2017

I tried everything to resolve this (except the last solution, too late now), my solution was to put my shiny new Lenovo Laptop on Craigslist, sell it, and buy a Macbook Pro.

I hope someone from Microsoft is seeing this, Windows 10 is bad. I don't think this is a docker problem as much as a Microsoft problem, they seemed to have changed something in windows 10 that makes the shares not work as they should.

@videni

This comment has been minimized.

Show comment
Hide comment
@videni

videni May 17, 2017

@pmcdowell-okta, I agree, development in windows10 is a hell.

videni commented May 17, 2017

@pmcdowell-okta, I agree, development in windows10 is a hell.

@prajapatin

This comment has been minimized.

Show comment
Hide comment
@prajapatin

prajapatin Oct 25, 2017

After lot of struggle, I was able to get rid of this error. Please follow below steps if none of the resolution works mentioned on this thread.

Navigate to C:\Users\Public\Documents\Hyper-V (it will ask administrative permission)
Click on folder "Virtual hard disks"
Here you will find "MobyLinuxVM.vhdx", just right click on it and goto context menu "Share with -> Advanced sharing settings..."
There you just go ahead and enable sharing under Public folder sharing blade and that's it. Once you have saved this settings, go ahead and enable sharing drive through docker command or through docker UI (settings)

prajapatin commented Oct 25, 2017

After lot of struggle, I was able to get rid of this error. Please follow below steps if none of the resolution works mentioned on this thread.

Navigate to C:\Users\Public\Documents\Hyper-V (it will ask administrative permission)
Click on folder "Virtual hard disks"
Here you will find "MobyLinuxVM.vhdx", just right click on it and goto context menu "Share with -> Advanced sharing settings..."
There you just go ahead and enable sharing under Public folder sharing blade and that's it. Once you have saved this settings, go ahead and enable sharing drive through docker command or through docker UI (settings)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment