Diagnostics ID: 2C869355-4761-4177-87F0-1D12AA05B7D2/20200504173718ĭocker container should be bonded with the selected IP address and port Actual behaviourĭocker does some magic and bind container with random port and 127.0.0.1 IP address.

In production you get support with Docker Enterprise Edition, and the Windows Server 2016 licence includes Docker EE Basic so you can raise support tickets with Microsoft and have them escalated to Docker, Inc.

I have tried with the latest version of my channel (Stable or Edge) Docker for Windows is a free Docker Community Edition, and runs on Windows 10 and Windows Server 2016.

So, why is it not possible to bind an IP address to a container? The inspect sub-commands of docker are extremely helpful. There are a couple of ways you can check the IP addresses associated with your container, here is a list of all of them including command examples. Actual behavior The browser cannot connect to the address. Then I can check that address on the host machine and it is possible to get a response from nc tool. Checking your docker container's IP address. Expected behavior When a simple webserver container is started and port 80 is exposed he host should become reachable at localhost:80 or 127.0.0.1:80. The following example uses sqlcmd to connect to SQL Server running in a Docker container. On bare WSL2 I can assign an additional IP address to the network interface and listen on that address even with simply nc tool. SQL Server deployments in Windows containers are not covered by support. Why is it not possible to use -p 123.123.123.123:80:80 within docker anymore? After using docker run -p ip_address:port:port docker generate random port and use 127.0.0.1 address. Okay, I'm after a few days with WSL2 and latest Docker Edge with WSL backend and I'm so disappointed.

Windows 10 docker container ip address