This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi everyone, I recently installed docker on a machine running on Windows Server 2016 by following this guide: https://learn.microsoft.com/en-us/virtualization/windowscontainers/quick-start/set-up-environment?tabs=Windows-Server After successfully installing docker, I proceeded with the next guide to run my first container: https://learn.microsoft.com/en-us/virtualization/windowscontainers/quick-start/run-your-first-container Every step in this guide also worked, with the exception that I used this image "mcr.microsoft.com/windows/servercore:1607" instead of the nanoserver suggested, because my machine runs on the version 1607 - OS build 14393.3808, and seems like I needed an image supported my OS version. Anyway, I'm able to pull images, run the container and work with it. The problem arises with networking, because it seems like my server (which is also the host for docker) can't reach the container's address. I was told that if everything works properly, I should be able to: - ping container's Default Gateway from the host (works) - ping container's IP Address from the host (doesn't work) - ping host's IP Address from inside the container (works) - ping container's Default Gateway from inside the container (doesn't work) The screenshots below will show you the results mentioned above. Commands run inside the container: ![17761-windowsticket2.png][1] Commands run from the host (scw000100860): ![17704-windowsticket3.png][2] I have already set the NetIPInterface so that the interface that accesses internet has the lowest InterfaceMetric value. ![17705-windowsticket1.png][3] These were the things I was told from the software provider that my company needs to install. The software runs multiple containers but seems like they're not reachable so the tool obviously won't work, but they told me the issue is on docker side, since I'm not able to ping any container's IP Address from the host. Please let me know what I can do to fix this issue or if I can provide more information to you. Thanks a lot in advance. Nicolò [1]: /api/attachments/17761-windowsticket2.png?platform=QnA [2]: /api/attachments/17704-windowsticket3.png?platform=QnA [3]: /api/attachments/17705-windowsticket1.png?platform=QnA
Hi,
I am doing research and trying to test in my lab, it will take some time to do research, if I get any update, I will update as soon as possible. Thanks for your patience.
Best Regards,
Anne
Dear XiaoweiHe-MSFT,
Thanks for your answer and for taking time to help me with this issue.
Is there an update following the research and tests you're performing?
Unfortunately I'm going to vacation at the end of this week and I won't be able to progress on this topic for the following 2 weeks, which is also going to block all my colleagues with the installation of the software I mentioned in the beginning. Please let me know if I can provide you more information or help you in any way to save some time on your tests.
Thanks a lot.
Nicolò
Hi,
To be honest, since docker case is few and I didn't have much experience on docker, I need some time to research from scratch, if you can provide the step by step command to create the lab, I will reproduce your scenario soon and do more research.
What's more, it will be better if you can provide the result of the command below:
docker service ls
docker service ps test
docker network ls
Thanks for your understanding!
Best Regards,
Anne
Hello,
Thanks for replying. The steps to reproduce my scenario are mentioned in the beginning, all I did was following Windows guides on how to install Docker and run a container for Windows Server 2016.
The only 2 notes I can add are:
Everything else seems to work as expected and gives no issues, until I try to perform the pings I reported in my question. Here's the result of the commands you asked for: ![19077-windowsticket4.png][1] [1]: /answers/storage/temp/19077-windowsticket4.png Please let me know if I can do more. Thanks, Nicolò (posting 2 separate replies because it had to many chars)
Hi,
As far as I'm concerned, we may try to create a customized NAT network, and run the container in the customized NAT network.
docker network create --driver=nat <name>
Since I get some error to run the container, I am still testing, you may also try in your docker.
https://docs.docker.com/engine/tutorials/networkingcontainers/
Hey,
Thanks a lot for providing these additional steps and sorry for replying so late, as I mentioned I was on vacation.
I tried creating a custom NAT network driver, and then proceeded to remove the container I'm doing these tests with from the default NAT network and added it to the new custom one. It worked because I can see by inspecting the new network that it has my container, and also inspecting the container I see it uses the new driver.
Unfortunately, besides changing the IP Address used by the container and the gateway, the ping tests give the same results: I can still ping the gateway from the host, but can't ping container's IP.
The rest of the tutorial you linked seem to be about network linking 2 separate containers, but it's not my case since I'm trying to reach 1 container only from the host.
Have you got any other idea?
Thanks in advance,
Nicolò