[Bug 1156112] New: Docker does not work after boot.
http://bugzilla.opensuse.org/show_bug.cgi?id=1156112 Bug ID: 1156112 Summary: Docker does not work after boot. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner@suse.de Reporter: miso@hlavki.eu QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After some Tumbleweed snapshot docker stopped work after boot. I have to restart docker service to get it work. Error: Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:39602->[::1]:53: read: connection refused -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1156112
http://bugzilla.opensuse.org/show_bug.cgi?id=1156112#c1
Klaus Kämpf
dig registry-1.docker.io on this system's command line ?
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1156112
http://bugzilla.opensuse.org/show_bug.cgi?id=1156112#c2
Michal Hlavac
http://bugzilla.opensuse.org/show_bug.cgi?id=1156112
http://bugzilla.opensuse.org/show_bug.cgi?id=1156112#c3
--- Comment #3 from Michal Hlavac
http://bugzilla.opensuse.org/show_bug.cgi?id=1156112
Andrey Karepin
http://bugzilla.opensuse.org/show_bug.cgi?id=1156112
http://bugzilla.opensuse.org/show_bug.cgi?id=1156112#c4
Aleksa Sarai
hlavki@hlknb:~> docker pull alpine Using default tag: latest Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:44874->[::1]:53: read: connection refused
But dig is doing lookups through IPv4 to 192.168.10.1 (is that your local machine?):
hlavki@hlknb:~> dig registry-1.docker.io [snip] ;; Query time: 54 msec ;; SERVER: 192.168.10.1#53(192.168.10.1) ;; WHEN: Fri Nov 08 08:51:42 CET 2019 ;; MSG SIZE rcvd: 177
Can you connect to localhost via IPv6, and what is your resolv.conf setup? Do you have a DNS server running locally (to block ads or something)? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1156112
http://bugzilla.opensuse.org/show_bug.cgi?id=1156112#c5
--- Comment #5 from Aleksa Sarai
http://bugzilla.opensuse.org/show_bug.cgi?id=1156112
http://bugzilla.opensuse.org/show_bug.cgi?id=1156112#c6
--- Comment #6 from Michal Hlavac
http://bugzilla.opensuse.org/show_bug.cgi?id=1156112
http://bugzilla.opensuse.org/show_bug.cgi?id=1156112#c7
--- Comment #7 from Aleksa Sarai
Hi Aleksa,
thanks for reply.
1. 192.168.10.1 is IP of my home router
Okay, so it's definitely the case that Docker (for whatever reason) is misunderstanding your DNS configuration.
2. Now I am out of my home network, but this problem occurs everywhere.
/etc/resolv.conf is generated:
### /etc/resolv.conf is a symlink to /var/run/netconfig/resolv.conf ### autogenerated by netconfig! # # Before you change this file manually, consider to define the # static DNS configuration using the following variables in the # /etc/sysconfig/network/config file: # NETCONFIG_DNS_STATIC_SEARCHLIST # NETCONFIG_DNS_STATIC_SERVERS # NETCONFIG_DNS_FORWARDER # or disable DNS configuration updates via netconfig by setting: # NETCONFIG_DNS_POLICY='' # # See also the netconfig(8) manual page and other documentation. # ### Call "netconfig update -f" to force adjusting of /etc/resolv.conf. nameserver 195.80.171.4 nameserver 195.28.64.119
I guess at home this file would contain "nameserver 192.168.10.1"?
I have not local DNS server. What do you mean by connect to localhost via IPv6. I tried ping and it works: hlavki@hlknb:~> ping6 ::1 PING ::1(::1) 56 data bytes 64 bytes from ::1: icmp_seq=1 ttl=64 time=0.077 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.070 ms
::1 is like 127.0.0.1 but for IPv6 (it's your local machine) -- it's not very surprising that you can ping it :P. I meant trying to force a DNS lookup to your localhost to see if it fails outside Docker as well. You'd do it with something like: % dig @::1 +short registry-1.docker.io But I imagine this will give you a timeout error.
3. When I restart docker daemon, it starts to work. Maybe problem is that network connection is made after docker daemon starts.
I guess Docker might cache the DNS server to try (but this happens before resolv.conf is configured) -- if you try to pull an image a few times in a row (without restarting) does it eventually work? Or is it constantly broken until you restart? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1156112
http://bugzilla.opensuse.org/show_bug.cgi?id=1156112#c8
--- Comment #8 from Michal Hlavac
I guess at home this file would contain "nameserver 192.168.10.1"?
Yes
% dig @::1 +short registry-1.docker.io But I imagine this will give you a timeout error.
Yes, connection timed out; no servers could be reached
I guess Docker might cache the DNS server to try (but this happens before resolv.conf is configured) -- if you try to pull an image a few times in a row (without restarting) does it eventually work? Or is it constantly broken until you restart?
if I try to pull an image later, it starts to work -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1156112
http://bugzilla.opensuse.org/show_bug.cgi?id=1156112#c9
Aleksa Sarai
http://bugzilla.opensuse.org/show_bug.cgi?id=1156112
John Paul Adrian Glaubitz
participants (2)
-
bugzilla_noreply@novell.com
-
bugzilla_noreply@suse.com