We have a problem about resolv.conf，we added resolving servers in web admin when creating container, but it was commented out for no reason, anyone here got this problem before?

Archive Rancher 1.x
1

rancher version 1.2
rancher agent version 0.8.3

2

up up

no one get this problem before?

3

Hi, running into the same issue. Any update on this?

4

They’re not commented out for “no reason”, they’re commented out because the container’s DNS is configured to point at the Network Agent, which resolves internal service discovery names (*.rancher.internal) itself. Other requests are proxied to the resolvers configured for the container or host.