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

Windows 10: Docker for Windows: unable to share drive #690

Closed
pip7p opened this Issue May 1, 2017 · 39 comments

Comments

Projects
None yet
@pip7p

pip7p commented May 1, 2017

Expected behavior

Sharing a drive using Settings > Shared Drives

Actual behavior

UI asks for Credentials, Hangs for a bit, then unchecks all the drives automatically

(like in #114, but different error-message appears in the log files )

Information

Recently updated Windows

Diagnostic-ID 4C664C5C-648E-4B3C-B3D0-430B2437DB46/2017-05-01_16-45-52

Error-Message from Logfile:
[16:38:46.811][SambaShare ][Error ] Unable to mount D drive: container_linux.go:247: starting container process caused "exec: \"/usr/bin/nsenter1\": stat /usr/bin/nsenter1: no such file or directory" C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "exec: \"/usr/bin/nsenter1\": stat /usr/bin/nsenter1: no such file or directory".

Windows-Version 10 Pro, Version 1703, Build 15063.250

Steps to reproduce the behavior

  1. Go To Settings
  2. Mark a drive to be shared
  3. Press Apply button
  4. Provide credentials when asked
  5. Be disappointed
@lgaida

This comment has been minimized.

Show comment
Hide comment
@lgaida

lgaida May 2, 2017

@pip7p i got the same issue today and could resolve it by uninstalling and installing the edge-channel version of Docker for Windows.

lgaida commented May 2, 2017

@pip7p i got the same issue today and could resolve it by uninstalling and installing the edge-channel version of Docker for Windows.

@pip7p

This comment has been minimized.

Show comment
Hide comment
@pip7p

pip7p May 2, 2017

@lgrepo Thanks for the tip!

  • I uninstalled docker (stable here)

  • rebooted (you know, because windows)

  • installed docker edge

Now it's working again.

pip7p commented May 2, 2017

@lgrepo Thanks for the tip!

  • I uninstalled docker (stable here)

  • rebooted (you know, because windows)

  • installed docker edge

Now it's working again.

@Dargmuesli

This comment has been minimized.

Show comment
Hide comment
@Dargmuesli

Dargmuesli Jul 14, 2017

With the latest update (version 17.06.0-ce-win19 (12801), Channel: stable, c98c1c2) I've got the exactly same issue.
The latest available edge build is version 17.06.0-ce-win17 so it does not fix anything / reopens other issues (see mentioned above).

What I did:

  1. Install Docker
  2. Start Docker with or without reboot before that
  3. Share a drive: no credentials dialog pops up, drive is marked as shared.
  4. Restart Docker
  5. Share a drive: a credentials dialog pops up, the drive's share checkbox is automatically unchecked.

No firewall warning dialog.

Diagnostic ID: EFBB7AB3-04A0-48F9-A61E-8E855D80D797/2017-07-14_02-09-19

Error message in log file:

[02:09:11.167][SambaShare     ][Error  ] Unable to mount H drive: container_linux.go:262: starting container process caused "exec: \"/usr/bin/nsenter1\": stat /usr/bin/nsenter1: no such file or directory"
C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: oci runtime error: container_linux.go:262: starting container process caused "exec: \"/usr/bin/nsenter1\": stat /usr/bin/nsenter1: no such file or directory".

Dargmuesli commented Jul 14, 2017

With the latest update (version 17.06.0-ce-win19 (12801), Channel: stable, c98c1c2) I've got the exactly same issue.
The latest available edge build is version 17.06.0-ce-win17 so it does not fix anything / reopens other issues (see mentioned above).

What I did:

  1. Install Docker
  2. Start Docker with or without reboot before that
  3. Share a drive: no credentials dialog pops up, drive is marked as shared.
  4. Restart Docker
  5. Share a drive: a credentials dialog pops up, the drive's share checkbox is automatically unchecked.

No firewall warning dialog.

Diagnostic ID: EFBB7AB3-04A0-48F9-A61E-8E855D80D797/2017-07-14_02-09-19

Error message in log file:

[02:09:11.167][SambaShare     ][Error  ] Unable to mount H drive: container_linux.go:262: starting container process caused "exec: \"/usr/bin/nsenter1\": stat /usr/bin/nsenter1: no such file or directory"
C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: oci runtime error: container_linux.go:262: starting container process caused "exec: \"/usr/bin/nsenter1\": stat /usr/bin/nsenter1: no such file or directory".
@lgaida

This comment has been minimized.

Show comment
Hide comment
@lgaida

lgaida Jul 25, 2017

@Dargmuesli take a look at #803, same issue, other workaround(s)

lgaida commented Jul 25, 2017

@Dargmuesli take a look at #803, same issue, other workaround(s)

@Dargmuesli

This comment has been minimized.

Show comment
Hide comment
@Dargmuesli

Dargmuesli Jul 25, 2017

@lgrepo thank you for the hint, but unfortunately those workarounds did not work for me.

Dargmuesli commented Jul 25, 2017

@lgrepo thank you for the hint, but unfortunately those workarounds did not work for me.

@Dargmuesli

This comment has been minimized.

Show comment
Hide comment
@Dargmuesli

Dargmuesli Jul 25, 2017

The newest Edge build fixed the issue for me. Version 17.06.1-ce-rc1-win20 (12818).

Dargmuesli commented Jul 25, 2017

The newest Edge build fixed the issue for me. Version 17.06.1-ce-rc1-win20 (12818).

@solovis-ggipson

This comment has been minimized.

Show comment
Hide comment
@solovis-ggipson

solovis-ggipson Nov 28, 2017

was not fixed - still occurs in 17.09.0-ce-win33 (13620)

C:\WINDOWS\system32> docker run --rm -v c:/Users:/data alpine ls /data
C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: An error occured while sharing drive.
See 'C:\Program Files\Docker\Docker\Resources\bin\docker.exe run --help'.

solovis-ggipson commented Nov 28, 2017

was not fixed - still occurs in 17.09.0-ce-win33 (13620)

C:\WINDOWS\system32> docker run --rm -v c:/Users:/data alpine ls /data
C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: An error occured while sharing drive.
See 'C:\Program Files\Docker\Docker\Resources\bin\docker.exe run --help'.

@e-gautier

This comment has been minimized.

Show comment
Hide comment
@e-gautier

e-gautier Dec 2, 2017

Still occurs in 17.09.0-ce-win33 (13620).

e-gautier commented Dec 2, 2017

Still occurs in 17.09.0-ce-win33 (13620).

@jdebarochez

This comment has been minimized.

Show comment
Hide comment
@jdebarochez

jdebarochez Dec 3, 2017

I've disabled the experimental features of the daemon and it worked.

jdebarochez commented Dec 3, 2017

I've disabled the experimental features of the daemon and it worked.

@e-gautier

This comment has been minimized.

Show comment
Hide comment
@e-gautier

e-gautier Dec 3, 2017

Log file:

umount: can't unmount /c: Invalid argument
umount: can't unmount /C: Invalid argument
mount error(95): Not supported
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
mount: mounting //x.x.x.x/C on /c failed: Invalid argument

I want to specify that I haven't done any custom configuration, I just installed Docker and tried to share C drive.

e-gautier commented Dec 3, 2017

Log file:

umount: can't unmount /c: Invalid argument
umount: can't unmount /C: Invalid argument
mount error(95): Not supported
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
mount: mounting //x.x.x.x/C on /c failed: Invalid argument

I want to specify that I haven't done any custom configuration, I just installed Docker and tried to share C drive.

@miestr

This comment has been minimized.

Show comment
Hide comment
@miestr

miestr Dec 19, 2017

Still getting the error with the latest stable docker version on Windows 10. Resetting docker to factory defaults solves the issue, but as soon as I create containers, mounting C starts failing again.
Unable to mount C drive: container_linux.go:265: starting container process caused "exec: \"/usr/bin/nsenter1\": stat /usr/bin/nsenter1: no such file or directory" C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: oci runtime error: container_linux.go:265: starting container process caused "exec: \"/usr/bin/nsenter1\": stat /usr/bin/nsenter1: no such file or directory".

miestr commented Dec 19, 2017

Still getting the error with the latest stable docker version on Windows 10. Resetting docker to factory defaults solves the issue, but as soon as I create containers, mounting C starts failing again.
Unable to mount C drive: container_linux.go:265: starting container process caused "exec: \"/usr/bin/nsenter1\": stat /usr/bin/nsenter1: no such file or directory" C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: oci runtime error: container_linux.go:265: starting container process caused "exec: \"/usr/bin/nsenter1\": stat /usr/bin/nsenter1: no such file or directory".

@msgeissler

This comment has been minimized.

Show comment
Hide comment
@msgeissler

msgeissler Jan 17, 2018

This is still happening on 17.12.0-ce-win47, current stable version.
Disabling experimental features as suggested by jdebarochez did not help.
Already tried resetting Docker because other things broke after the update...

Unable to mount D drive: C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: OCI runtime create failed: container_linux.go:296: starting container process caused "exec: \"/usr/bin/nsenter1\": stat /usr/bin/nsenter1: no such file or directory": unknown.

msgeissler commented Jan 17, 2018

This is still happening on 17.12.0-ce-win47, current stable version.
Disabling experimental features as suggested by jdebarochez did not help.
Already tried resetting Docker because other things broke after the update...

Unable to mount D drive: C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: OCI runtime create failed: container_linux.go:296: starting container process caused "exec: \"/usr/bin/nsenter1\": stat /usr/bin/nsenter1: no such file or directory": unknown.

@mankajatt

This comment has been minimized.

Show comment
Hide comment
@mankajatt

mankajatt Jan 23, 2018

Same issues as msgeissler, moved over to Centos, dockeron windows a pain if cannot mount

Anyone with a resolution?

mankajatt commented Jan 23, 2018

Same issues as msgeissler, moved over to Centos, dockeron windows a pain if cannot mount

Anyone with a resolution?

@ThomasDK81

This comment has been minimized.

Show comment
Hide comment
@ThomasDK81

ThomasDK81 Jan 26, 2018

+1
Switching to Edge didn't work.

ThomasDK81 commented Jan 26, 2018

+1
Switching to Edge didn't work.

@kewp

This comment has been minimized.

Show comment
Hide comment
@kewp

kewp Jan 27, 2018

Same. Switching to Edge didn't work.

[20:30:28.748][SambaShare ][Error ] Unable to validate cred: Invalid username or password

kewp commented Jan 27, 2018

Same. Switching to Edge didn't work.

[20:30:28.748][SambaShare ][Error ] Unable to validate cred: Invalid username or password

@thefron

This comment has been minimized.

Show comment
Hide comment
@thefron

thefron Feb 2, 2018

+1. Not working on current stable version(17.12.0-ce-win47 (15139))

thefron commented Feb 2, 2018

+1. Not working on current stable version(17.12.0-ce-win47 (15139))

@jochenvanwylick

This comment has been minimized.

Show comment
Hide comment
@jochenvanwylick

jochenvanwylick Feb 3, 2018

Also still on 18.02.0-ce-rc2-win51 (15631) unfortunately

jochenvanwylick commented Feb 3, 2018

Also still on 18.02.0-ce-rc2-win51 (15631) unfortunately

@z3niths

This comment has been minimized.

Show comment
Hide comment
@z3niths

z3niths Feb 6, 2018

Same problem here 17.12.0-ce-win47

z3niths commented Feb 6, 2018

Same problem here 17.12.0-ce-win47

@jochenvanwylick

This comment has been minimized.

Show comment
Hide comment
@jochenvanwylick

jochenvanwylick Feb 9, 2018

Just got the update ( Version 18.02.0-ce-win52 (15732) ) - but still there

jochenvanwylick commented Feb 9, 2018

Just got the update ( Version 18.02.0-ce-win52 (15732) ) - but still there

@nhmaha

This comment has been minimized.

Show comment
Hide comment
@nhmaha

nhmaha Feb 9, 2018

Windows 10: 15063.608
Docker: 18.02.0-ce, build fc4de44


[USER_HOME]\AppData\Local\Docker\log.txt

[09:28:19.736][SambaShare ][Info ] Removing share D
[09:28:19.845][SambaShare ][Info ] Mount D
[09:28:19.906][Cmd ][Info ] This shared resource does not exist.
[09:28:19.906][Cmd ][Info ] More help is available by typing NET HELPMSG 2310.
[09:28:19.911][SambaShare ][Info ] "D" is not shared
[09:28:19.911][SambaShare ][Info ] Creating share "D:" as "D" with Full Control to "USER_NAME_REMOVED"
[09:28:20.008][Cmd ][Info ] D was shared successfully.
[09:28:20.071][Cmd ][Info ] Share name D
[09:28:20.071][Cmd ][Info ] Path D:
[09:28:20.071][Cmd ][Info ] Remark
[09:28:20.071][Cmd ][Info ] Maximum users No limit
[09:28:20.072][Cmd ][Info ] Users
[09:28:20.072][Cmd ][Info ] Caching Caching disabled
[09:28:20.072][Cmd ][Info ] Permission DOMAIN_REMOVED\USER_NAME_REMOVED, FULL
[09:28:20.072][Cmd ][Info ] The command completed successfully.
[09:28:20.080][SambaShare ][Info ] "D" is shared
[09:28:20.221][SambaShare ][Info ] Username: USER_NAME_REMOVED
[09:28:20.223][SambaShare ][Info ] Host IP: 10.0.75.1
[09:28:20.223][SambaShare ][Info ] Cifs options: noperm,iocharset=utf8,nobrl,mfsymlinks,vers=3.02,domain=ST,sec=ntlmsspi
[09:28:20.399][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="proxy >> GET /_ping\n"
[09:28:20.399][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Dial Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.400][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Successfully dialed Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.401][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="proxy << GET /_ping\n"
[09:28:20.404][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="proxy >> POST /v1.36/images/load?quiet=1\n"
[09:28:20.404][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Dial Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.407][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Successfully dialed Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.543][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="proxy << POST /v1.36/images/load?quiet=1\n"
[09:28:20.732][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="proxy >> GET /_ping\n"
[09:28:20.732][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Dial Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.733][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Successfully dialed Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.734][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="proxy << GET /_ping\n"
[09:28:20.737][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="proxy >> POST /v1.36/containers/create [rewriteBinds]\n"
[09:28:20.738][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Rewrote mount /run/config/docker:/host_mnt (volumeDriver=) to /run/config/docker:/host_mnt\n"
[09:28:20.738][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="proxy >> POST /v1.36/containers/create\n"
[09:28:20.738][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Dial Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.739][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Successfully dialed Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.896][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="proxy << POST /v1.36/containers/create\n"
[09:28:20.905][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="proxy >> POST /v1.36/containers/4c98ea478fe343d8fdc6a75af1044f5f4bb2f49e35453c014ab5f3e92c58195a/attach?stderr=1&stdin=1&stdout=1&stream=1\n"
[09:28:20.905][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Dial Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.906][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Successfully dialed Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.909][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Upgrading to raw stream"
[09:28:20.910][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="proxy >> POST /v1.36/containers/4c98ea478fe343d8fdc6a75af1044f5f4bb2f49e35453c014ab5f3e92c58195a/wait?condition=removed\n"
[09:28:20.910][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Dial Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.914][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Successfully dialed Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.916][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="proxy >> POST /v1.36/containers/4c98ea478fe343d8fdc6a75af1044f5f4bb2f49e35453c014ab5f3e92c58195a/start [start]\n"
[09:28:20.917][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="proxy >> POST /v1.36/containers/4c98ea478fe343d8fdc6a75af1044f5f4bb2f49e35453c014ab5f3e92c58195a/start\n"
[09:28:20.917][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Dial Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.918][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Successfully dialed Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.958][Moby ][Info ] [ 86.367752] docker0: port 1(veth37b7735) entered blocking state
[09:28:20.983][Moby ][Info ] [ 86.388615] docker0: port 1(veth37b7735) entered disabled state
[09:28:20.999][Moby ][Info ] [ 86.414421] device veth37b7735 entered promiscuous mode
[09:28:21.016][Moby ][Info ] [ 86.431557] IPv6: ADDRCONF(NETDEV_UP): veth37b7735: link is not ready
[09:28:21.031][Moby ][Info ] [ 86.447019] docker0: port 1(veth37b7735) entered blocking state
[09:28:21.057][Moby ][Info ] [ 86.462449] docker0: port 1(veth37b7735) entered forwarding state
[09:28:21.089][Moby ][Info ] [ 86.489621] docker0: port 1(veth37b7735) entered disabled state
[09:28:21.215][Moby ][Info ] [ 86.607605] IPVS: Creating netns size=2104 id=14
[09:28:21.234][Moby ][Info ] [ 86.647426] IPVS: ftp: loaded support on port[0] = 21
[09:28:21.376][Moby ][Info ] [ 86.770715] eth0: renamed from veth3671a69
[09:28:21.468][Moby ][Info ] [ 86.850669] IPv6: ADDRCONF(NETDEV_CHANGE): veth37b7735: link becomes ready
[09:28:21.495][Moby ][Info ] [ 86.900362] docker0: port 1(veth37b7735) entered blocking state
[09:28:21.513][Moby ][Info ] [ 86.926470] docker0: port 1(veth37b7735) entered forwarding state
[09:28:21.619][ApiProxy ][Info ] time="2018-02-09T09:28:21-08:00" msg="proxy << POST /v1.36/containers/4c98ea478fe343d8fdc6a75af1044f5f4bb2f49e35453c014ab5f3e92c58195a/start\n"
[09:28:21.761][Moby ][Info ] [ 87.164245] CIFS VFS: No username specified
[09:28:21.796][Moby ][Info ] [ 87.204805] Status code returned 0xc000015b STATUS_LOGON_TYPE_NOT_GRANTED
[09:28:21.808][Moby ][Info ] [ 87.227901] CIFS VFS: Send error in SessSetup = -5
[09:28:21.825][Moby ][Info ] [ 87.240046] CIFS VFS: cifs_mount failed w/return code = -5
[09:28:21.859][ApiProxy ][Info ] time="2018-02-09T09:28:21-08:00" msg="proxy << POST /v1.36/containers/4c98ea478fe343d8fdc6a75af1044f5f4bb2f49e35453c014ab5f3e92c58195a/attach?stderr=1&stdin=1&stdout=1&stream=1\n"
[09:28:21.925][Moby ][Info ] [ 87.337370] docker0: port 1(veth37b7735) entered disabled state
[09:28:21.938][Moby ][Info ] [ 87.356744] veth3671a69: renamed from eth0
[09:28:22.112][Moby ][Info ] [ 87.515204] docker0: port 1(veth37b7735) entered disabled state
[09:28:22.139][Moby ][Info ] [ 87.544082] device veth37b7735 left promiscuous mode
[09:28:22.160][Moby ][Info ] [ 87.570353] docker0: port 1(veth37b7735) entered disabled state
[09:28:22.576][ApiProxy ][Info ] time="2018-02-09T09:28:22-08:00" msg="proxy << POST /v1.36/containers/4c98ea478fe343d8fdc6a75af1044f5f4bb2f49e35453c014ab5f3e92c58195a/wait?condition=removed\n"
[09:28:22.602][SambaShare ][Error ] Unable to mount D drive: 10.0.75.1 (10.0.75.1:445) open
rm: can't remove '/d': No such file or directory
rm: can't remove '/D': No such file or directory
umount: can't unmount /host_mnt/d: Invalid argument
mount error(5): I/O error
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
mount: mounting //10.0.75.1/D on /host_mnt/d failed: Invalid argument

[09:28:22.602][SambaShare ][Info ] Removing share D
[09:28:22.685][NamedPipeClient][Info ] Received response for Mount
[09:28:22.685][NamedPipeServer][Info ] Mount done in 00:00:06.1972430.
[09:28:22.691][ApiProxy ][Info ] time="2018-02-09T09:28:22-08:00" msg="An error occured while sharing drive"

nhmaha commented Feb 9, 2018

Windows 10: 15063.608
Docker: 18.02.0-ce, build fc4de44


[USER_HOME]\AppData\Local\Docker\log.txt

[09:28:19.736][SambaShare ][Info ] Removing share D
[09:28:19.845][SambaShare ][Info ] Mount D
[09:28:19.906][Cmd ][Info ] This shared resource does not exist.
[09:28:19.906][Cmd ][Info ] More help is available by typing NET HELPMSG 2310.
[09:28:19.911][SambaShare ][Info ] "D" is not shared
[09:28:19.911][SambaShare ][Info ] Creating share "D:" as "D" with Full Control to "USER_NAME_REMOVED"
[09:28:20.008][Cmd ][Info ] D was shared successfully.
[09:28:20.071][Cmd ][Info ] Share name D
[09:28:20.071][Cmd ][Info ] Path D:
[09:28:20.071][Cmd ][Info ] Remark
[09:28:20.071][Cmd ][Info ] Maximum users No limit
[09:28:20.072][Cmd ][Info ] Users
[09:28:20.072][Cmd ][Info ] Caching Caching disabled
[09:28:20.072][Cmd ][Info ] Permission DOMAIN_REMOVED\USER_NAME_REMOVED, FULL
[09:28:20.072][Cmd ][Info ] The command completed successfully.
[09:28:20.080][SambaShare ][Info ] "D" is shared
[09:28:20.221][SambaShare ][Info ] Username: USER_NAME_REMOVED
[09:28:20.223][SambaShare ][Info ] Host IP: 10.0.75.1
[09:28:20.223][SambaShare ][Info ] Cifs options: noperm,iocharset=utf8,nobrl,mfsymlinks,vers=3.02,domain=ST,sec=ntlmsspi
[09:28:20.399][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="proxy >> GET /_ping\n"
[09:28:20.399][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Dial Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.400][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Successfully dialed Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.401][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="proxy << GET /_ping\n"
[09:28:20.404][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="proxy >> POST /v1.36/images/load?quiet=1\n"
[09:28:20.404][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Dial Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.407][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Successfully dialed Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.543][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="proxy << POST /v1.36/images/load?quiet=1\n"
[09:28:20.732][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="proxy >> GET /_ping\n"
[09:28:20.732][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Dial Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.733][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Successfully dialed Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.734][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="proxy << GET /_ping\n"
[09:28:20.737][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="proxy >> POST /v1.36/containers/create [rewriteBinds]\n"
[09:28:20.738][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Rewrote mount /run/config/docker:/host_mnt (volumeDriver=) to /run/config/docker:/host_mnt\n"
[09:28:20.738][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="proxy >> POST /v1.36/containers/create\n"
[09:28:20.738][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Dial Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.739][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Successfully dialed Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.896][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="proxy << POST /v1.36/containers/create\n"
[09:28:20.905][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="proxy >> POST /v1.36/containers/4c98ea478fe343d8fdc6a75af1044f5f4bb2f49e35453c014ab5f3e92c58195a/attach?stderr=1&stdin=1&stdout=1&stream=1\n"
[09:28:20.905][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Dial Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.906][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Successfully dialed Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.909][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Upgrading to raw stream"
[09:28:20.910][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="proxy >> POST /v1.36/containers/4c98ea478fe343d8fdc6a75af1044f5f4bb2f49e35453c014ab5f3e92c58195a/wait?condition=removed\n"
[09:28:20.910][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Dial Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.914][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Successfully dialed Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.916][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="proxy >> POST /v1.36/containers/4c98ea478fe343d8fdc6a75af1044f5f4bb2f49e35453c014ab5f3e92c58195a/start [start]\n"
[09:28:20.917][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="proxy >> POST /v1.36/containers/4c98ea478fe343d8fdc6a75af1044f5f4bb2f49e35453c014ab5f3e92c58195a/start\n"
[09:28:20.917][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Dial Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.918][ApiProxy ][Info ] time="2018-02-09T09:28:20-08:00" msg="Successfully dialed Hyper-V socket abb893c2-52bd-473b-83fb-00e77dddf817:23a432c2-537a-4291-bcb5-d62504644739"
[09:28:20.958][Moby ][Info ] [ 86.367752] docker0: port 1(veth37b7735) entered blocking state
[09:28:20.983][Moby ][Info ] [ 86.388615] docker0: port 1(veth37b7735) entered disabled state
[09:28:20.999][Moby ][Info ] [ 86.414421] device veth37b7735 entered promiscuous mode
[09:28:21.016][Moby ][Info ] [ 86.431557] IPv6: ADDRCONF(NETDEV_UP): veth37b7735: link is not ready
[09:28:21.031][Moby ][Info ] [ 86.447019] docker0: port 1(veth37b7735) entered blocking state
[09:28:21.057][Moby ][Info ] [ 86.462449] docker0: port 1(veth37b7735) entered forwarding state
[09:28:21.089][Moby ][Info ] [ 86.489621] docker0: port 1(veth37b7735) entered disabled state
[09:28:21.215][Moby ][Info ] [ 86.607605] IPVS: Creating netns size=2104 id=14
[09:28:21.234][Moby ][Info ] [ 86.647426] IPVS: ftp: loaded support on port[0] = 21
[09:28:21.376][Moby ][Info ] [ 86.770715] eth0: renamed from veth3671a69
[09:28:21.468][Moby ][Info ] [ 86.850669] IPv6: ADDRCONF(NETDEV_CHANGE): veth37b7735: link becomes ready
[09:28:21.495][Moby ][Info ] [ 86.900362] docker0: port 1(veth37b7735) entered blocking state
[09:28:21.513][Moby ][Info ] [ 86.926470] docker0: port 1(veth37b7735) entered forwarding state
[09:28:21.619][ApiProxy ][Info ] time="2018-02-09T09:28:21-08:00" msg="proxy << POST /v1.36/containers/4c98ea478fe343d8fdc6a75af1044f5f4bb2f49e35453c014ab5f3e92c58195a/start\n"
[09:28:21.761][Moby ][Info ] [ 87.164245] CIFS VFS: No username specified
[09:28:21.796][Moby ][Info ] [ 87.204805] Status code returned 0xc000015b STATUS_LOGON_TYPE_NOT_GRANTED
[09:28:21.808][Moby ][Info ] [ 87.227901] CIFS VFS: Send error in SessSetup = -5
[09:28:21.825][Moby ][Info ] [ 87.240046] CIFS VFS: cifs_mount failed w/return code = -5
[09:28:21.859][ApiProxy ][Info ] time="2018-02-09T09:28:21-08:00" msg="proxy << POST /v1.36/containers/4c98ea478fe343d8fdc6a75af1044f5f4bb2f49e35453c014ab5f3e92c58195a/attach?stderr=1&stdin=1&stdout=1&stream=1\n"
[09:28:21.925][Moby ][Info ] [ 87.337370] docker0: port 1(veth37b7735) entered disabled state
[09:28:21.938][Moby ][Info ] [ 87.356744] veth3671a69: renamed from eth0
[09:28:22.112][Moby ][Info ] [ 87.515204] docker0: port 1(veth37b7735) entered disabled state
[09:28:22.139][Moby ][Info ] [ 87.544082] device veth37b7735 left promiscuous mode
[09:28:22.160][Moby ][Info ] [ 87.570353] docker0: port 1(veth37b7735) entered disabled state
[09:28:22.576][ApiProxy ][Info ] time="2018-02-09T09:28:22-08:00" msg="proxy << POST /v1.36/containers/4c98ea478fe343d8fdc6a75af1044f5f4bb2f49e35453c014ab5f3e92c58195a/wait?condition=removed\n"
[09:28:22.602][SambaShare ][Error ] Unable to mount D drive: 10.0.75.1 (10.0.75.1:445) open
rm: can't remove '/d': No such file or directory
rm: can't remove '/D': No such file or directory
umount: can't unmount /host_mnt/d: Invalid argument
mount error(5): I/O error
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
mount: mounting //10.0.75.1/D on /host_mnt/d failed: Invalid argument

[09:28:22.602][SambaShare ][Info ] Removing share D
[09:28:22.685][NamedPipeClient][Info ] Received response for Mount
[09:28:22.685][NamedPipeServer][Info ] Mount done in 00:00:06.1972430.
[09:28:22.691][ApiProxy ][Info ] time="2018-02-09T09:28:22-08:00" msg="An error occured while sharing drive"

@VladoDemcak

This comment has been minimized.

Show comment
Hide comment
@VladoDemcak

VladoDemcak commented Feb 10, 2018

same issue as @nhmaha

@drenzul

This comment has been minimized.

Show comment
Hide comment
@drenzul

drenzul Feb 15, 2018

Also same issue

drenzul commented Feb 15, 2018

Also same issue

@thefron

This comment has been minimized.

Show comment
Hide comment
@thefron

thefron Feb 19, 2018

Just to note, my primary windows account is bound to my university organization which requires custom sign in. After creating a new windows user using normal windows account, it worked fine.

thefron commented Feb 19, 2018

Just to note, my primary windows account is bound to my university organization which requires custom sign in. After creating a new windows user using normal windows account, it worked fine.

@BiggerHeader

This comment has been minimized.

Show comment
Hide comment
@BiggerHeader

BiggerHeader Mar 8, 2018

also same issue

BiggerHeader commented Mar 8, 2018

also same issue

@NickvdMeij

This comment has been minimized.

Show comment
Hide comment
@NickvdMeij

NickvdMeij Mar 12, 2018

same here

Version 17.12.0-ce-win47 (15139)
Channel: stable
9c692cd

NickvdMeij commented Mar 12, 2018

same here

Version 17.12.0-ce-win47 (15139)
Channel: stable
9c692cd

@snpdev

This comment has been minimized.

Show comment
Hide comment
@snpdev

snpdev Mar 14, 2018

@NickvdMeij, I am on the same version as you - 17.12.0-ce-win47 (15139).

This solution worked for me: #803 (comment).

I would just one more step - after adding the new user to the Administrators group, you need to actually log in as the user for the Administrators group to take effect. I switched to the new user to initialize it, and then switched back to my regular account.

snpdev commented Mar 14, 2018

@NickvdMeij, I am on the same version as you - 17.12.0-ce-win47 (15139).

This solution worked for me: #803 (comment).

I would just one more step - after adding the new user to the Administrators group, you need to actually log in as the user for the Administrators group to take effect. I switched to the new user to initialize it, and then switched back to my regular account.

@NickvdMeij

This comment has been minimized.

Show comment
Hide comment
@NickvdMeij

NickvdMeij Mar 14, 2018

@snpdev Hey, already fixed this issue yesterday already but thanks for the info ^^

I indeed used another account for this, like you mentioned. Only had to reset docker to factory settings afterwards to get it to work, and it works like a charm now (even after reboot).

NickvdMeij commented Mar 14, 2018

@snpdev Hey, already fixed this issue yesterday already but thanks for the info ^^

I indeed used another account for this, like you mentioned. Only had to reset docker to factory settings afterwards to get it to work, and it works like a charm now (even after reboot).

@PetRichBlog

This comment has been minimized.

Show comment
Hide comment
@PetRichBlog

PetRichBlog Apr 12, 2018

Hello everybody! For get decision need next step: share your all disk, which you try share in Docker setting (Right click button for disk which you want share, and choose Properties->Sharing->Advanced Sharing and check "Share this folder" next click Permissions->Everyone and check Allow->FullControl ). And restart docker. And else you can make vhd disk in manage panel, and connect it with this permissions.

PetRichBlog commented Apr 12, 2018

Hello everybody! For get decision need next step: share your all disk, which you try share in Docker setting (Right click button for disk which you want share, and choose Properties->Sharing->Advanced Sharing and check "Share this folder" next click Permissions->Everyone and check Allow->FullControl ). And restart docker. And else you can make vhd disk in manage panel, and connect it with this permissions.

@Smilebags

This comment has been minimized.

Show comment
Hide comment
@Smilebags

Smilebags May 5, 2018

Hi, I'm also having the same issue and the fix by @PetRichBlog didn't seem to work.
Win10, 64bit, admin user, stable channel of Docker.

Smilebags commented May 5, 2018

Hi, I'm also having the same issue and the fix by @PetRichBlog didn't seem to work.
Win10, 64bit, admin user, stable channel of Docker.

@shadowmint

This comment has been minimized.

Show comment
Hide comment
@shadowmint

shadowmint May 9, 2018

I'm also having this issue; but it's intermittent.

Basically, to reproduce:

  • Docker windows settings -> Shared drives -> Share a drive.
  • Now change your password
  • Go back into settings 'reset credentials'
  • Now attempt to click on the drive and pick 'share'

You'll notice that doing this, the little 'shared' checkbox is never checked, no matter how many times you hit apply and enter your password; if you close the settings and open them again, it remains unchecked.

Work around:

  • Shutdown docker completely.
  • Restart docker.
  • Docker settings -> Drives -> share the drive
  • Apply

I can't say if this works for anyone else, but it seems to me the docker daemon gets into a 'screwed up state' where it is confused about what credentials should be used.

Restarting the daemon appears to revert to clean slate and allow drives to be shared again.

...however, I'll add that intermittently I get this after a system restart as well, and once again it requires a manual restart of the daemon.

Hopefully that is helpful to others seeing this issue and to generate a repro to drive a bug fix for it.

shadowmint commented May 9, 2018

I'm also having this issue; but it's intermittent.

Basically, to reproduce:

  • Docker windows settings -> Shared drives -> Share a drive.
  • Now change your password
  • Go back into settings 'reset credentials'
  • Now attempt to click on the drive and pick 'share'

You'll notice that doing this, the little 'shared' checkbox is never checked, no matter how many times you hit apply and enter your password; if you close the settings and open them again, it remains unchecked.

Work around:

  • Shutdown docker completely.
  • Restart docker.
  • Docker settings -> Drives -> share the drive
  • Apply

I can't say if this works for anyone else, but it seems to me the docker daemon gets into a 'screwed up state' where it is confused about what credentials should be used.

Restarting the daemon appears to revert to clean slate and allow drives to be shared again.

...however, I'll add that intermittently I get this after a system restart as well, and once again it requires a manual restart of the daemon.

Hopefully that is helpful to others seeing this issue and to generate a repro to drive a bug fix for it.

@LiamKarlMitchell

This comment has been minimized.

Show comment
Hide comment
@LiamKarlMitchell

LiamKarlMitchell Jun 2, 2018

still a problem why does it need C drive anyway my docker files are on E.

This solved it, although it had some weirdness as it still wanted access to my C drive...
http://peterjohnlightfoot.com/docker-for-windows-on-hyper-v-fix-the-host-volume-sharing-issue/

I just left the computer name. But the login seems like it was exactly the same as my normal windows login other than being named "Docker User".

ERROR: for docker-magento2_apache_1  Cannot start service apache: error while creating mount source path '/host_mnt/c/Users/megab/.composer/auth.json': mkdir /host_mnt/c/Users/megab/.composer: permission denied

I enabled the Experimental features of the Docker Daemon which caused it to restart if that made a difference...

LiamKarlMitchell commented Jun 2, 2018

still a problem why does it need C drive anyway my docker files are on E.

This solved it, although it had some weirdness as it still wanted access to my C drive...
http://peterjohnlightfoot.com/docker-for-windows-on-hyper-v-fix-the-host-volume-sharing-issue/

I just left the computer name. But the login seems like it was exactly the same as my normal windows login other than being named "Docker User".

ERROR: for docker-magento2_apache_1  Cannot start service apache: error while creating mount source path '/host_mnt/c/Users/megab/.composer/auth.json': mkdir /host_mnt/c/Users/megab/.composer: permission denied

I enabled the Experimental features of the Docker Daemon which caused it to restart if that made a difference...

@carljmosca

This comment has been minimized.

Show comment
Hide comment
@carljmosca

carljmosca Jul 9, 2018

I am currently running Version 18.03.1-ce-win65 (17513) and it appears that this is still and issue. I have seen this before and I have tried a variety of approaches. I recall finding the "Server" service not running. Most recently I changed startup type (of the "Server" service) to Automatic (it was previously disabled). I then restarted Windows and was able to share the drive.

carljmosca commented Jul 9, 2018

I am currently running Version 18.03.1-ce-win65 (17513) and it appears that this is still and issue. I have seen this before and I have tried a variety of approaches. I recall finding the "Server" service not running. Most recently I changed startup type (of the "Server" service) to Automatic (it was previously disabled). I then restarted Windows and was able to share the drive.

@mpp-oliverh

This comment has been minimized.

Show comment
Hide comment
@mpp-oliverh

mpp-oliverh Aug 2, 2018

I've never once managed to get the Windows drive sharing working, I've tried all the suggested workarounds over the last year. This issue certainly shouldn't be closed!

mpp-oliverh commented Aug 2, 2018

I've never once managed to get the Windows drive sharing working, I've tried all the suggested workarounds over the last year. This issue certainly shouldn't be closed!

@carljmosca

This comment has been minimized.

Show comment
Hide comment
@carljmosca

carljmosca Aug 2, 2018

I know of a couple others who tried the "Server" service (which apparently has more than one name) that I describe above and it get them going as it did me.

carljmosca commented Aug 2, 2018

I know of a couple others who tried the "Server" service (which apparently has more than one name) that I describe above and it get them going as it did me.

@jjgriff93

This comment has been minimized.

Show comment
Hide comment
@jjgriff93

jjgriff93 Sep 2, 2018

Also getting exactly this issue, agree this is not resolved and should NOT be closed.

jjgriff93 commented Sep 2, 2018

Also getting exactly this issue, agree this is not resolved and should NOT be closed.

@izikorgad

This comment has been minimized.

Show comment
Hide comment
@izikorgad

izikorgad Sep 5, 2018

  • 1
    Still happens...
    Please reopen this issue.

izikorgad commented Sep 5, 2018

  • 1
    Still happens...
    Please reopen this issue.
@carljmosca

This comment has been minimized.

Show comment
Hide comment
@carljmosca

carljmosca Sep 5, 2018

Got tired of being ignored: #2549

carljmosca commented Sep 5, 2018

Got tired of being ignored: #2549

@orontee

This comment has been minimized.

Show comment
Hide comment
@orontee

orontee Sep 20, 2018

Same bug here

orontee commented Sep 20, 2018

Same bug here

@Citizen-icon

This comment has been minimized.

Show comment
Hide comment
@Citizen-icon

Citizen-icon Sep 21, 2018

Same

[15:07:58.879][SambaShare ][Error ] Unable to mount D drive: C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: "/usr/bin/nsenter1": stat /usr/bin/nsenter1: no such file or directory": unknown.

Citizen-icon commented Sep 21, 2018

Same

[15:07:58.879][SambaShare ][Error ] Unable to mount D drive: C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: "/usr/bin/nsenter1": stat /usr/bin/nsenter1: no such file or directory": unknown.

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