rancher: dns resolution is not working in any container

rancher/server:v0.50.0 rancher/agent:v0.8.2 rancher/agent-instance:v0.6.0

Tested with the catalog service route53 using as hosts custom server, but the error happens also with any other container.

d1f35b74e747        rancher/external-dns:v0.1.7     "/usr/bin/external-dn"   About an hour ago   Up About a minute                                                  770fe0c4-ee6c-4c1f-a27b-b491a90d7791
[root@node-3 ~]# docker logs 770fe0c4-ee6c-4c1f-a27b-b491a90d7791
time="2015-12-15T22:19:47Z" level=fatal msg="Failed to configure rancher-metadata: Get http://rancher-metadata/latest/version: dial tcp: i/o timeout"
docker exec -it 770fe0c4-ee6c-4c1f-a27b-b491a90d7791 sh
 cat /etc/resolv.conf
# nameserver 213.186.33.99
search ovh.net rancher.internal
nameserver 169.254.169.250
nslookup
> server 169.254.169.250
Default server: 169.254.169.250
Address: 169.254.169.250#53
> rancher-metadata
;; reply from unexpected source: 10.42.180.3#53, expected 169.254.169.250#53
;; reply from unexpected source: 10.42.180.3#53, expected 169.254.169.250#53
;; reply from unexpected source: 10.42.180.3#53, expected 169.254.169.250#53
;; connection timed out; trying next origin
;; reply from unexpected source: 10.42.180.3#53, expected 169.254.169.250#53
;; connection timed out; no servers could be reached
root@node-3 ~]# cat /etc/*release
CentOS Linux release 7.2.1511 (Core)
[root@node-3 ~]# docker version
Client:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   a34a1d5
 Built:        Fri Nov 20 13:25:01 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   a34a1d5
 Built:        Fri Nov 20 13:25:01 UTC 2015
 OS/Arch:      linux/amd64

About this issue

  • Original URL
  • State: closed
  • Created 9 years ago
  • Comments: 16 (6 by maintainers)

Most upvoted comments

Just adding a note here. I’m also an OVH customer and was running into this issue using their Debian Jessie image.

When reinstalling the OS on an OVH server there is an option for advanced mode to which you can pick to use the distribution kernel rather than OVH’s custom kernel which solved the issue for me.

Figured I’d add that here for any future Googlers looking for help 😃

@mcuadros , glad you were able to get isolate this issue. Happy New Year !!

@deniseschannon , can we add documentation regarding the kernel modules required for iptable rules.