search

docker / for-win

Bug reports for Docker Desktop for Windows
https://www.docker.com/products/docker#/windows
1.86k stars 290 forks source link

Map TCP port to host ip not working (Edge) #5114

Closed edrevo closed 4 years ago

edrevo commented 5 years ago

Expected behavior

Port forwarding bound to a specific IP address should work.

Actual behavior

failed programming external connectivity on endpoint fervent_easley (44aec7ef6f293cf0c5e1fa828ca378b108e9826aa076a713070fbbe16e6804f1): Error starting userland proxy: listen tcp 192.168.1.23:80: bind: cannot assign requested address.

Information

I get the same behavior both in the MobyVM daemon and in the WSL2 daemon. I wasn't able to reproduce this issue on the lastest stable versions of Docker and Win10.

I have 2 IPs set in my network adapter, but I removed one of them to see if the issue disappeared and it still happened. Binding to 127.0.0.1 did work though.

Steps to reproduce the behavior

  1. docker run --rm -it -p 192.168.1.23:9090:9090 alpine sh
simonferquel commented 4 years ago

@djs55 can you have a look at this one ?

marekmartins commented 4 years ago

Any news regarding this? I have similar issue. I'm using the latest Edge version (2.1.7.0), running in WSL 2 mode.

docker-robott commented 4 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale comment. Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle stale

docker-robott commented 4 years ago

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