So, find out what IP you are using in that specific network, make sure that it is static or the router remembers the IP it allocated you and use the rule above (replace YOUR_NETWORK_IP with your network IP, duh!): netsh interface portproxy add v4tov4 listenaddress=YOUR_NETWORK_IP listenport=80 connectaddress=192.168.99.100 connectport=80 For localhost works like a charm, however, if you wish to make the docker container accessible from within the network, Windows Operating System will give you yet another pain in the back.įirst of all, you will need to make a port redirect not from localhost, but from your external network interface. List all forwards: netsh interface portproxy show v4tov4Īnd delete the ones you don’t need anymore: netsh interface portproxy delete v4tov4 listenaddress=127.0.0.1 listenport=80īut, as explained, this is not all.
netsh interface portproxy add v4tov4 listenaddress=127.0.0.1 listenport=80 connectaddress=192.168.99.100 connectport=80 Using Windows Powershell or the old cmd, you can port forward your localhost port to the ip of the virtual machine. So here it comes, part one of the solution. So back to Google again, where we found a post by Dmytro Nemoga mentioning about a command named netsh which could port redirect localhost or any other network interface from the computer to the network interface used by the Docker virtual machine.
I think it is obvious that we were not the only ones confronting with this problem, and hence we first encountered this issue the docker community evolved.
So I had my doubts again whether to upgrade his OS or not. This can be easily achieved under Windows Pro hence HyperV and Docker for Windows tool have a different setup which allow us to use the container port publish under ‘localhost’ directly. Long story short, the application had to be run on docker, however accessed on a domain like ‘’, which also made it accessible not only to my developer as well as the rest of the group. This recently changed when one of my employees was forced to work for a while from within a client’s network, and even more, work under Windows while the application was to be accessed under network designated domains only. For a long time we avoided using Docker Toolkbox because we didn’t understand how to allow the containers created within the docker Virtual Box machine by using local host and not the virtual machine’s ip (usually 192.168.99.100).
0 kommentar(er)
