localhost force bind about for-win HOT 5 CLOSED

It's because your Windows machine is already running SMB on port 445. That means the port is in use, and the docker container cannot bind to it. Disabling port 445 would not work since Docker for Windows relies on the host SMB server to do volume sharing.

Can you not map your container SMB server to a different port.

from for-win.

@friism I guess I can, but the question is bind to localhost is a good idea? I think this should be optional like before because unlike mac, widows uses so many ports by default.

from for-win.

@adithep we want using Docker to be a consistent experience across platforms, and we want running Docker containers to feel like running any other app.

I'm closing this issue for now, feel free to follow up if you have concerns.

from for-win.

@friism Can I make a request then to make localhost optional for both mac and windows version? Should I create a new issue? I think there is nothing wrong with having ability to turn off localhost bind. I am having no problem with the mac version so far but I am already considering moving back to docker toolbox on windows machine because of this. It disrupts a lot of my workflow.

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.