SOLVED: Mounting directories on Windows 10 do not seem to work about for-win HOT 10 CLOSED

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?

from for-win.

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.

from for-win.

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

from for-win.

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?

from for-win.

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

from for-win.

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.

from for-win.

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

from for-win.

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

from for-win.

@simonferquel awesome, thx

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.