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

SOLVED: Mounting directories on Windows 10 do not seem to work #50

Closed
michaelwiller opened this Issue Aug 20, 2016 · 9 comments

Comments

Projects
None yet
5 participants
@michaelwiller

michaelwiller commented Aug 20, 2016

docker run --rm -v c:/Users/michael:/data alpine ls -la /data

Expected behavior

List of C:\Users\michael
ls

Actual behavior

Only showing "." and "..".

ls

Information

  • Diagnostic ID from "Diagnose & Feedback" in the menu.

F72D0B33-B1B3-4168-B9E8-D812A10C0166/2016-08-21_00-03-22

Docker version is:

Client:
Version: 1.12.1-rc1
API version: 1.24
Go version: go1.6.3
Git commit: 7889dc7
Built: Fri Aug 12 18:35:53 2016
OS/Arch: windows/amd64
Experimental: true

Server:
Version: 1.12.1-rc1
API version: 1.24
Go version: go1.6.3
Git commit: 7889dc7
Built: Fri Aug 12 18:35:53 2016
OS/Arch: linux/amd64
Experimental: true

(switched to Beta, since this didn't work in stable 1.12)

  • host distribution and version (Windows version, build number, etc)

Confirm that C: is shared. And user SCOTT-TIGER-MW\michael has full control.
ls

Password of "michael" is very short and has no special characters.

Observation:
System reacts to C:/Users/not-found just as it reacts to C:/Users/michael ... It can't see anything in the share.

Tried to use share as "net use X: \SCOTT-TIGER-MW\michael\C"; dir X:\Users\michael. This worked as expected (list of content displayed).

Steps to reproduce the behavior

  1. docker run --rm -v c:/Users/michael:/data alpine ls -la /data

I have tried entering credentials in settings with and without machine-name. Docker seems to be using the machine-name just fine. But none of the options work.

@michaelwiller

This comment has been minimized.

Show comment
Hide comment
@michaelwiller

michaelwiller Aug 20, 2016

Disabling Norton firewall and auto-protect allows the share to work. Even works with Norton protection reenabled. Restart Docker and the connection is lost again.
I have trust set up for com.docker.proxy, slirp and Docker for Windows.
Q: What traffic do I need to allow through?

michaelwiller commented Aug 20, 2016

Disabling Norton firewall and auto-protect allows the share to work. Even works with Norton protection reenabled. Restart Docker and the connection is lost again.
I have trust set up for com.docker.proxy, slirp and Docker for Windows.
Q: What traffic do I need to allow through?

@michaelwiller

This comment has been minimized.

Show comment
Hide comment
@michaelwiller

michaelwiller Aug 21, 2016

I have created a rule in the firewall allowing incoming traffic for TCP/UPD on ports 139,445 on net 10.0.75.0/24. This seems to resolve matters.

Can anyone think of a better way?

michaelwiller commented Aug 21, 2016

I have created a rule in the firewall allowing incoming traffic for TCP/UPD on ports 139,445 on net 10.0.75.0/24. This seems to resolve matters.

Can anyone think of a better way?

@yetanotherchris

This comment has been minimized.

Show comment
Hide comment
@yetanotherchris

yetanotherchris Aug 21, 2016

I was having the exact same problem as @michaelwiller but trying to map to a folder on C:

docker run -it -v /C/Code/Nginx/logstash:/config-dir logstash bash -c "ls /config-dir"

The firewall rules fixed it (along with a Docker restart). I'm not tying it down to an IP.

yetanotherchris commented Aug 21, 2016

I was having the exact same problem as @michaelwiller but trying to map to a folder on C:

docker run -it -v /C/Code/Nginx/logstash:/config-dir logstash bash -c "ls /config-dir"

The firewall rules fixed it (along with a Docker restart). I'm not tying it down to an IP.

@michaelwiller michaelwiller changed the title from Mounting directories on Windows 10 do not seem to work to SOLVED: Mounting directories on Windows 10 do not seem to work Aug 21, 2016

@michaelwiller

This comment has been minimized.

Show comment
Hide comment
@michaelwiller

michaelwiller Aug 21, 2016

Glad I could help :)
This is why I left it open. Closing the issue and prefixing with "SOLVED:"

michaelwiller commented Aug 21, 2016

Glad I could help :)
This is why I left it open. Closing the issue and prefixing with "SOLVED:"

@yetanotherchris

This comment has been minimized.

Show comment
Hide comment
@yetanotherchris

yetanotherchris Aug 22, 2016

For anyone viewing this, here's two lines of powershell for the firewall rule:

 New-NetFirewallRule -DisplayName "Docker For-Win TCP" -Direction Inbound –LocalPort 139, 445 -Protocol TCP -Action Allow
 New-NetFirewallRule -DisplayName "Docker For-Win UDP" -Direction Inbound –LocalPort 139, 445 -Protocol UDP -Action Allow

yetanotherchris commented Aug 22, 2016

For anyone viewing this, here's two lines of powershell for the firewall rule:

 New-NetFirewallRule -DisplayName "Docker For-Win TCP" -Direction Inbound –LocalPort 139, 445 -Protocol TCP -Action Allow
 New-NetFirewallRule -DisplayName "Docker For-Win UDP" -Direction Inbound –LocalPort 139, 445 -Protocol UDP -Action Allow
@lypanov

This comment has been minimized.

Show comment
Hide comment
@lypanov

lypanov Dec 18, 2016

The above Powershell should really be in the documentation. It's just not enough to have to search for 10 minutes to find this Github issue.

lypanov commented Dec 18, 2016

The above Powershell should really be in the documentation. It's just not enough to have to search for 10 minutes to find this Github issue.

@friism

This comment has been minimized.

Show comment
Hide comment
@friism

friism Dec 18, 2016

@simonferquel could we auto-open these ports during install?

friism commented Dec 18, 2016

@simonferquel could we auto-open these ports during install?

@simonferquel

This comment has been minimized.

Show comment
Hide comment
@simonferquel

simonferquel Dec 19, 2016

@friism it is already done on beta channel (and stable 1.13 will have it)

simonferquel commented Dec 19, 2016

@friism it is already done on beta channel (and stable 1.13 will have it)

@friism

This comment has been minimized.

Show comment
Hide comment
@friism

friism commented Dec 19, 2016

@simonferquel awesome, thx

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