HNSEndpoint DNSServerList is ignored in 10.0.17733 about hcsshim HOT 2 CLOSED

@arjun024 Can you add the commands to create the container and network?
I've tried to repro on 17733 and couldn't repro. I tried the following:

1. docker run -d --rm -it --network none --name test windowsservercore powershell sleep 50000
2. nat.
3. docker exec test ipconfig /all
   DNS Servers . . . . . . . . . . . : 222.111.111.222
   123.123.123.123

And, I also tried creating my own nat network using:
docker network create --driver=nat n

And I get the same result as above.

Thanks.

from hcsshim.

@pradipd thank you for trying this out. We were able to reproduce the behavior that you saw above using the mcr.microsoft.com/windowsservercore-insider:10.0.17733.1000 container image.

However, this issue seems to still exist when we disable the dnscache service in a child container image. When we add this line in a Dockerfile that uses mcr.microsoft.com/windowsservercore-insider:10.0.17733.1000 as its base image, we are able to reproduce the original behavior that we reported in this github issue. We originally made this change to our container image to resolve DNS flakiness from inside the container (see #150). Per the most recent comment in that github issue, it sounds like we can keep the dnscache service on in our container image. We will try this going forward.

from hcsshim.