Windows Container with Docker: Cannot reach httpd in container from host (Win2016 TP5) -
i have windows server 2016 tp5 machine use container host.
i have windows container running manage docker. inside container have apache httpd running on port 88.
the port mapping when start container is: 0.0.0.0:80->88/tcp
, map port 80 of container host port 88 of container. output docker inspect
: http://pastebin.com/avem1egv
i can reach apache http start page other computer in network through dns or ip.
in case:
but same not work when try call same host system or inside container. so, on host system, try access same url via browser or wget, , getting:
c:\> wget -usebasicparsing http://documents.test2016-3.company.com/ wget : unable connect remote server
in both cases.
but can ping host both host container.
from host:
c:\>ping test2016-3.company.com ping wird ausgeführt für test2016-3.company.com [fe80::847a:1430:8a10:b120%4] mit 32 bytes daten:
from container:
ps c:\> ping documents.test2016-3.company.com pinging documents.test2016-3.company.com [10.10.1.162] 32 bytes of data:
which seems able resolve name fine.
what does work though call apache default page via container hostname (which win-de6u4068naf) , running port directly (not through port mapping), both host inside container:
just going route through container host hostname , mapped port host or container not work properly!
firewall rules allow on port 80 remote address or port 80 (=inbound , outbound rules both set "allow" "any").
i know microsoft/docker changed networking code base of container/docker support windows server 2016 tp4 tp5. not sure if that's related, or whether bug or i'm having not configured correctly yet.
i made test , left docker/container out of picture above , installed plain apache httpd on container host system on port 80 (and no docker running @ all) check whether such setup works or not, in order sure somehow docker/container related , not problem network/host configuration in general. , works fine, can reach apache outside host itself, must docker/container related problem.
environment:
- windows server 2016 tp5
- docker version 1.12.0-dev, build 2b97201
got reply on microsoft's github:
https://github.com/microsoft/virtualization-documentation/issues/253#issuecomment-217975932
this known limitation in our windows nat implementation (winnat) cannot access external port in static port mapping directly container (nat) host.
Comments
Post a Comment