service-fabric: DNS doesn't work in containers

I have: Windows 10, Docker for Windows CE, Latest Service Fabric SDK and a local single node cluster.

I create two asp.net core services and deploy them to Service Fabric as container hosts:

    <EntryPoint>
      <ContainerHost>
        <ImageName>webapplication2:dev</ImageName>
      </ContainerHost>
    </EntryPoint>

If I connect to the running containers using docker exec and try pinging the configured DNS names, I get no response. If I use PowerShell and try: Invoke-WebRequest http://the_dns_name I also get no response. These things work fine when using the IP address.

Is this a configuration issue or am I trying to do something that can’t be done and if it can’t be done then how is it possible to sensibly resolve container endpoints?

About this issue

Original URL
State: open
Created 6 years ago
Reactions: 5
Comments: 26

Most upvoted comments

Not very helpful, I know, but I gave up in the end and switched to Kubernetes. There’s some short term pain involved but it’s worth it in the long run.

chaholl on Sep 3, 2019