Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 192.168.65.1:53: server misbehaving #1317

Closed
nabedge opened this issue Feb 21, 2017 · 120 comments

Comments

@nabedge
Copy link

@nabedge nabedge commented Feb 21, 2017

$ uname -a
Darwin nabedge.local 16.4.0 Darwin Kernel Version 16.4.0: Thu Dec 22 22:53:21 PST 2016; root:xnu-3789.41.3~3/RELEASE_X86_64 x86_64
$ docker-compose --version
docker-compose version 1.11.1, build 7c5d5e4
$ docker --version
Docker version 1.13.1, build 092cba3
$ docker pull centos:6.8
Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 192.168.65.1:53: server misbehaving

Is this same bug ? #1025

@ijc ijc added the status/0-triage label Feb 21, 2017
@LevonBecker

This comment has been minimized.

Copy link

@LevonBecker LevonBecker commented Feb 22, 2017

I have the same issues. Uninstalled/Reset and Re-installed. Nutching diff.

macOS 10.12.3

docker version

Client:
Version: 1.13.1
API version: 1.26
Go version: go1.7.5
Git commit: 092cba3
Built: Wed Feb 8 08:47:51 2017
OS/Arch: darwin/amd64

Server:
Version: 1.13.1
API version: 1.26 (minimum version 1.12)
Go version: go1.7.5
Git commit: 092cba3
Built: Wed Feb 8 08:47:51 2017
OS/Arch: linux/amd64
Experimental: true

Errors

docker pull amazonlinux
Using default tag: latest
Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 192.168.65.1:53: server misbehaving

docker pull centos:6.8
Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 192.168.65.1:53: server misbehaving

@ijc

This comment has been minimized.

Copy link
Contributor

@ijc ijc commented Feb 22, 2017

@nabedge please use the 🐳 menu ➡️ `Diagnose and feedback" to upload a diagnostic log ball and add the output here.

@LevonBecker, please do the same but create a fresh issue, although your symptoms seem similar the underlying cause could be different and it is far easier to de-dup issues than it is to split a single issue into two.

@nabedge

This comment has been minimized.

Copy link
Author

@nabedge nabedge commented Feb 22, 2017

Thanks.
I have solved this problem by re-install (uninstall -> install) the same version docker.

@nabedge nabedge closed this Feb 22, 2017
@LevonBecker

This comment has been minimized.

Copy link

@LevonBecker LevonBecker commented Feb 22, 2017

sure thing

@nicksnyder

This comment has been minimized.

Copy link

@nicksnyder nicksnyder commented Feb 28, 2017

I just had the same problem and a re-install fixed it.

@rainder

This comment has been minimized.

Copy link

@rainder rainder commented Feb 28, 2017

have the same problem but re-installing does not help. Diagnose shows all OK

@ferbass

This comment has been minimized.

Copy link

@ferbass ferbass commented Feb 28, 2017

same problem after reinstall
Fixed when switching to beta version

@LevonBecker

This comment has been minimized.

Copy link

@LevonBecker LevonBecker commented Feb 28, 2017

clean reinstall (1.13.1) did not fix for me. Switching to beta version did fix it for me.

@rainder

This comment has been minimized.

Copy link

@rainder rainder commented Feb 28, 2017

my problem was fixed when I set 8.8.8.8 as a dns server

@LevonBecker

This comment has been minimized.

Copy link

@LevonBecker LevonBecker commented Feb 28, 2017

8.8.8.8 didn't fix mine... just installing beta. It's such a random issue with random solutions that work. Very odd /shrug

@MagnusS

This comment has been minimized.

Copy link
Contributor

@MagnusS MagnusS commented Mar 8, 2017

@nicksnyder @rainder @ferbass @LevonBecker There are several DNS fixes in the latest 17.03.x beta/stable releases, which may fix the issue for you. If you still experience problems with the latest version, please open new issues with a diagnostic ID. This is a closed issue and to figure out what is going on we would have to look at the logs. Thanks!

@ferbass

This comment has been minimized.

Copy link

@ferbass ferbass commented Mar 9, 2017

Thank you @MagnusS the problems was solved on this version to me

Version 17.03.0-ce-mac2 (15654) Channel: stable 1d7d97bbbd

@MikhailKaduchka

This comment has been minimized.

Copy link

@MikhailKaduchka MikhailKaduchka commented Mar 9, 2017

docker-machine ssh default
sudo vi /etc/resolv.conf

change nameserver to 8.8.8.8

@richarda23

This comment has been minimized.

Copy link

@richarda23 richarda23 commented Mar 10, 2017

Hi, I've just installed docker CE today, following instructions at https://docs.docker.com/engine/installation/linux/ubuntu/ and get this error as well when trying to run or pull anything.
Ubuntu 14.04LTS:

lsb_release -a
LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
Distributor ID: Ubuntu
Description: Ubuntu 14.04.4 LTS
Release: 14.04
Codename: trusty

Docker 17.03:
builder@kudu:~$ docker version
Client:
Version: 17.03.0-ce
API version: 1.26
Go version: go1.7.5
Git commit: 3a232c8
Built: Tue Feb 28 07:57:58 2017
OS/Arch: linux/amd64

Server:
Version: 17.03.0-ce
API version: 1.26 (minimum version 1.12)
Go version: go1.7.5
Git commit: 3a232c8
Built: Tue Feb 28 07:57:58 2017
OS/Arch: linux/amd64
Experimental: false

and /etc/resolve.cnf:
nameserver 8.8.8.8
nameserver 8.8.4.4

Any suggestions appreciated, thanks!

@ranaskr

This comment has been minimized.

Copy link

@ranaskr ranaskr commented Mar 16, 2017

I had the same error when I was running docker pull hello-world

root@someubuntumc:~# docker pull hello-world
Using default tag: latest
Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 127.0.1.1:53: no such host

I then realized that I did not configure proxy in the docker config file. Add these details to your docker config (depending on your os), I am using ubuntu so the file is - /etc/default/docker/

export http_proxy="http://user:pwd@proxyurl.com:port"
export https_proxy="https://user:pwd@proxy-url.com:port"

Restart docker (service docker restart) and this solved for me

@pnowy

This comment has been minimized.

Copy link

@pnowy pnowy commented Apr 16, 2017

DNS server set to 8.8.8.8 fix the problem for me (Win10)

@carusology

This comment has been minimized.

Copy link

@carusology carusology commented Apr 19, 2017

Same issue for Docker for Mac:

~$ docker pull ubuntu
Using default tag: latest
Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 192.168.65.1:53: read udp 192.168.65.2:47975->192.168.65.1:53: i/o timeout

Setting the DNS Server for the Docker Daemon via "Preferences > Daemon > Advanced" based upon advice given here by @thaJeztah via putting in the following value worked for me (no reinstall required):

{ "dns" : [ "8.8.8.8", "8.8.4.4" ]}
@umbruch

This comment has been minimized.

Copy link

@umbruch umbruch commented Apr 28, 2017

all this did not help me. If you are in a company behinde a proxy use this guide, it did solve my problem
https://docs.docker.com/engine/admin/systemd/#manually-creating-the-systemd-unit-files

@zatamine

This comment has been minimized.

Copy link

@zatamine zatamine commented May 25, 2017

I went lunch and it's worked when i'm back :D

@akki0996

This comment has been minimized.

Copy link

@akki0996 akki0996 commented Jul 5, 2017

Changing DNS server to 8.8.8.8 helped me. (Windows 10)

@omerlh

This comment has been minimized.

Copy link

@omerlh omerlh commented Jul 9, 2017

Changing DNS server to 8.8.8.8 on Docker settings helped also for me (Windows 10).

@lpcardinal

This comment has been minimized.

Copy link

@lpcardinal lpcardinal commented Jul 13, 2017

Re-installed docker and now it work.

@azamatsulaiman

This comment has been minimized.

Copy link

@azamatsulaiman azamatsulaiman commented Jul 14, 2017

solved restarting docker from settings (windows 10)

@veeshall

This comment has been minimized.

Copy link

@veeshall veeshall commented Jul 31, 2017

As commented by @MikhailKaduchka the below worked for on Windows 10

docker-machine ssh default
sudo vi /etc/resolv.conf

change nameserver to 8.8.8.8

@samsonkolge

This comment has been minimized.

Copy link

@samsonkolge samsonkolge commented Aug 3, 2017

If you are behind a proxy, please use the following link:
https://docs.docker.com/engine/admin/systemd/#httphttps-proxy

@kethansrinivas9

This comment has been minimized.

Copy link

@kethansrinivas9 kethansrinivas9 commented Aug 8, 2017

I am also using the Windows 10 machine but i haven't shifted my env to my External Virtual Machine in docker running the following command solved my issue
docker-machine env $MY_EXTERNAL_VIRTUAL_MACHINE_NAME$

@hardsv

This comment has been minimized.

Copy link

@hardsv hardsv commented Feb 23, 2019

I had the same issue with error
.docker\machine\machines\default\config.json: The system cannot find the file specified.

I have to go to my Oracle Virtual VM GUI and saw that there is a VM named 'default' which was running. I have to stop and delete it.
Now the docker quick start working fine.

Check following link for info:
https://stackoverflow.com/questions/40052629/docker-not-working-in-windows10

then doing what @tandon-aman said worked for me.

@digglife

This comment has been minimized.

Copy link

@digglife digglife commented Feb 27, 2019

I logged out my dockerhub account, and magically, it worked. WTF?

@data2601

This comment has been minimized.

Copy link

@data2601 data2601 commented Apr 2, 2019

I resolve it by editing /etc/resolv.conf file.
nameserver 8.8.8.8
nameserver 8.8.4.4
add two lines in above file.

@allamiro

This comment has been minimized.

Copy link

@allamiro allamiro commented Apr 7, 2019

my problem was fixed when I set 8.8.8.8 as a dns server

this fixed mine as I was using pfsense firewall

@draganstanisavljevic

This comment has been minimized.

Copy link

@draganstanisavljevic draganstanisavljevic commented Jun 4, 2019

I had same issue. The reason was VPN. After I disconnected from VPN, problem was fixed

@manishbansal8843

This comment has been minimized.

Copy link

@manishbansal8843 manishbansal8843 commented Jun 12, 2019

I am facing the same issue on a ubuntu linux VM on GCP. But it is not getting resolved. I have tried adding nameserver in /etc/resolv.conf, but it is still not working.

manishbansal8843@instance-1:~$ docker run hello-world
Unable to find image 'hello-world:latest' locally
docker: Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:38063->[::1]:53: read: connection refused.
@chandrauppaluru

This comment has been minimized.

Copy link

@chandrauppaluru chandrauppaluru commented Jul 16, 2019

reinstall worked for me

@carljdp

This comment has been minimized.

Copy link

@carljdp carljdp commented Jul 18, 2019

On Windows: Uninstall / reinstall solved it for me (+ setting proxy settings if on corporate network)

@amstrudy

This comment has been minimized.

Copy link

@amstrudy amstrudy commented Aug 2, 2019

For ROS users: This happened to me when I forgot to update the key. Make sure you have done that.

@harshsharma22

This comment has been minimized.

Copy link

@harshsharma22 harshsharma22 commented Aug 26, 2019

reinstall worked for me

@spookyGh0st

This comment has been minimized.

Copy link

@spookyGh0st spookyGh0st commented Sep 2, 2019

Turning off my vpn worked for me

@Tungtono

This comment has been minimized.

Copy link

@Tungtono Tungtono commented Sep 3, 2019

Restart Docker worked for me.

@furytara

This comment has been minimized.

Copy link

@furytara furytara commented Sep 21, 2019

"docker login" fix it

@talondnb

This comment has been minimized.

Copy link

@talondnb talondnb commented Oct 3, 2019

second attempt at the same command worked for me, odd!

@zhuyingda

This comment has been minimized.

Copy link

@zhuyingda zhuyingda commented Oct 28, 2019

Same issue for me.
Docker version: 19.03.4
MacOS version: 10.14.6

And reinstall(Preference>Reset>Uninstall> click same Docker.dmg to install) solved my problem~
Thanks.

@frostyaxe

This comment has been minimized.

Copy link

@frostyaxe frostyaxe commented Oct 31, 2019

As commented by @MikhailKaduchka the below worked for on Windows 10

docker-machine ssh default
sudo vi /etc/resolv.conf

change nameserver to 8.8.8.8

This has worked for me too. Thanks a lot mate. I owe you a beer ;)

@karippery

This comment has been minimized.

Copy link

@karippery karippery commented Nov 19, 2019

it work when I follow this doc: https://docs.docker.com/config/daemon/systemd/

@badrulhussain

This comment has been minimized.

Copy link

@badrulhussain badrulhussain commented Nov 20, 2019

Hi on my Windows Server 2019 running on AWS EC2 I managed to install docker using powershell and run the "docker run hello-world", which works fine.
but when I try to pull and run busybox i get this error
image

I have also tried changing DNS to 8.8.8.8
image

and even tried adding the 8.8.4.4 on alternate DNS. But I still get the same error.
I did this on both Ethernet and vEthernet.

The EC2 inbound and outbound traffic is set to all.

Does anyone know how to use docker on Windows server 2019?

@CompilationAnxiety

This comment has been minimized.

Copy link

@CompilationAnxiety CompilationAnxiety commented Nov 21, 2019

This have helped me:

If you are behind an HTTP or HTTPS proxy server, for example in corporate settings, you need to add this configuration in the Docker systemd service file.

  1. Create a systemd drop-in directory for the docker service:
$ sudo mkdir -p /etc/systemd/system/docker.service.d
  1. Create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY environment variable:
[Service]
Environment="HTTP_PROXY=http://proxy.example.com:80/"

Or, if you are behind an HTTPS proxy server, create a file called /etc/systemd/system/docker.service.d/https-proxy.conf that adds the HTTPS_PROXY environment variable:

[Service]
Environment="HTTPS_PROXY=https://proxy.example.com:443/"
  1. Flush changes:
$ sudo systemctl daemon-reload
  1. Restart Docker:
$ sudo systemctl restart docker

Source

@pmaidens

This comment has been minimized.

Copy link

@pmaidens pmaidens commented Dec 17, 2019

Ubuntu Docker CE

I ran into this problem after installing the Docker CE on Ubuntu.

Following the instruction here solved my issue.

tl;dr:

You need a /etc/docker/daemon.json file that contains

{
	"dns": ["8.8.8.8", "8.8.4.4"]
}

Then just restart docker sudo service docker restart.

@gunjan1004

This comment has been minimized.

Copy link

@gunjan1004 gunjan1004 commented Dec 17, 2019

Docker on Vagrant Ubuntu Box, Windows 10 Host

Same issue got resolved after adding the following entries in /etc/resolv.conf

  • nameserver 8.8.8.8
  • nameserver 8.8.4.4
@gnarr

This comment has been minimized.

Copy link

@gnarr gnarr commented Dec 31, 2019

Restart fixed this for me on Ubuntu Server 18.04 behind a pfSense

@fico7489

This comment has been minimized.

Copy link

@fico7489 fico7489 commented Jan 14, 2020

On Windows 10: It started to work when I changed my WIFI connection (not sure why)

@Dryobs

This comment has been minimized.

Copy link

@Dryobs Dryobs commented Jan 28, 2020

I had same issue on Ubuntu 16.04.
I simply stopped all my containers and the issue got resolved.

@incredimike

This comment has been minimized.

Copy link

@incredimike incredimike commented Feb 11, 2020

macOS Catalina 10.15.3
Docker upgraded using the built-in upgrade tool. Then this issue started. Downloading Docker fresh and installing it again fixed it.

@WHK102

This comment has been minimized.

Copy link

@WHK102 WHK102 commented Feb 16, 2020

Same problem from KVM image using CentOS7

[root@server ~]# docker -v
Docker version 19.03.6, build 369ce74a3c
[root@server ~]# ping -c 1 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=13.8 ms

--- 8.8.8.8 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 13.823/13.823/13.823/0.000 ms
[root@server ~]# cat /etc/docker/daemon.json
{
    "dns": ["8.8.8.8", "8.8.4.4"]
}
[root@server ~]# docker pull atlassian/jira-software
Using default tag: latest
Trying to pull repository docker.io/atlassian/jira-software ... 
Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 192.168.x.x:53: read udp 192.168.x.x:54328->192.168.x.x:53: i/o timeout
[root@server ~]# DOCKER_OPTS="--dns=8.8.8.8" docker pull atlassian/jira-software
Using default tag: latest
Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 192.168.x.x:53: read udp 192.168.x.x:46200->192.168.x.x:53: i/o timeout
[root@server ~]# dig -t A registry-1.docker.io @192.168.x.x

; <<>> DiG 9.11.4-P2-RedHat-9.11.4-9.P2.el7 <<>> -t A registry-1.docker.io @192.168.x.x
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7747
;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;registry-1.docker.io.		IN	A

;; ANSWER SECTION:
registry-1.docker.io.	42	IN	A	34.199.40.84
registry-1.docker.io.	42	IN	A	52.202.253.107
registry-1.docker.io.	42	IN	A	34.201.196.144
registry-1.docker.io.	42	IN	A	34.205.88.205
registry-1.docker.io.	42	IN	A	34.228.211.243
registry-1.docker.io.	42	IN	A	34.232.31.24
registry-1.docker.io.	42	IN	A	52.201.142.14
registry-1.docker.io.	42	IN	A	34.199.77.19

;; Query time: 0 msec
;; SERVER: 192.168.x.x#53(192.168.x.x)
;; WHEN: sáb feb 15 23:49:13 -03 2020
;; MSG SIZE  rcvd: 177

There is something curious to see the status of the firewalld service and it is that the docker rules commands have failed since installation. Is the connection to the DNS service due to a problem in the firewall rules applied automatically in the docker installation?

[root@server ~]# cat /var/log/firewalld
2020-02-15 23:04:43 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t nat -D OUTPUT -m addrtype --dst-type LOCAL ! --dst 127.0.0.0/8 -j DOCKER' failed: iptables v1.4.21: Couldn't load target `DOCKER':No such file or directory
Try `iptables -h' or 'iptables --help' for more information.
2020-02-15 23:04:43 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t nat -D OUTPUT -m addrtype --dst-type LOCAL -j DOCKER' failed: iptables v1.4.21: Couldn't load target `DOCKER':No such file or directory
Try `iptables -h' or 'iptables --help' for more information.
2020-02-15 23:04:43 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t nat -D PREROUTING' failed: iptables: Bad rule (does a matching rule exist in that chain?).
2020-02-15 23:04:43 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t nat -D OUTPUT' failed: iptables: Bad rule (does a matching rule exist in that chain?).
2020-02-15 23:04:43 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t nat -F DOCKER' failed: iptables: No chain/target/match by that name.
2020-02-15 23:04:43 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t nat -X DOCKER' failed: iptables: No chain/target/match by that name.
2020-02-15 23:04:43 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -F DOCKER' failed: iptables: No chain/target/match by that name.
2020-02-15 23:04:43 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -X DOCKER' failed: iptables: No chain/target/match by that name.
2020-02-15 23:04:43 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -F DOCKER-ISOLATION' failed: iptables: No chain/target/match by that name.
2020-02-15 23:04:43 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -X DOCKER-ISOLATION' failed: iptables: No chain/target/match by that name.
2020-02-15 23:04:43 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -D FORWARD -i docker0 -o docker0 -j DROP' failed: iptables: Bad rule (does a matching rule exist in that chain?).
2020-02-15 23:19:01 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t nat -D OUTPUT -m addrtype --dst-type LOCAL -j DOCKER' failed: iptables: No chain/target/match by that name.
2020-02-15 23:19:01 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t nat -D PREROUTING' failed: iptables: Bad rule (does a matching rule exist in that chain?).
2020-02-15 23:19:01 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t nat -D OUTPUT' failed: iptables: Bad rule (does a matching rule exist in that chain?).
2020-02-15 23:19:01 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -X DOCKER' failed: iptables: Too many links.
2020-02-15 23:19:01 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -X DOCKER-ISOLATION' failed: iptables: Too many links.
2020-02-15 23:19:01 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -D FORWARD -i docker0 -o docker0 -j DROP' failed: iptables: Bad rule (does a matching rule exist in that chain?).
2020-02-15 23:19:01 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -D FORWARD -i docker0 -o docker0 -j DROP' failed: iptables: Bad rule (does a matching rule exist in that chain?).
2020-02-15 23:33:57 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t nat -D OUTPUT -m addrtype --dst-type LOCAL -j DOCKER' failed: iptables: No chain/target/match by that name.
2020-02-15 23:33:57 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t nat -D PREROUTING' failed: iptables: Bad rule (does a matching rule exist in that chain?).
2020-02-15 23:33:57 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t nat -D OUTPUT' failed: iptables: Bad rule (does a matching rule exist in that chain?).
2020-02-15 23:33:57 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -X DOCKER' failed: iptables: Too many links.
2020-02-15 23:33:57 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -F DOCKER-ISOLATION-STAGE-1' failed: iptables: No chain/target/match by that name.
2020-02-15 23:33:57 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -X DOCKER-ISOLATION-STAGE-1' failed: iptables: No chain/target/match by that name.
2020-02-15 23:33:57 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -F DOCKER-ISOLATION-STAGE-2' failed: iptables: No chain/target/match by that name.
2020-02-15 23:33:57 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -X DOCKER-ISOLATION-STAGE-2' failed: iptables: No chain/target/match by that name.
2020-02-15 23:33:57 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -D FORWARD -i docker0 -o docker0 -j DROP' failed: iptables: Bad rule (does a matching rule exist in that chain?).
2020-02-15 23:33:57 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -D FORWARD -i docker0 -o docker0 -j DROP' failed: iptables: Bad rule (does a matching rule exist in that chain?).
2020-02-15 23:35:17 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t nat -D OUTPUT -m addrtype --dst-type LOCAL -j DOCKER' failed: iptables: No chain/target/match by that name.
2020-02-15 23:35:17 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t nat -D PREROUTING' failed: iptables: Bad rule (does a matching rule exist in that chain?).
2020-02-15 23:35:17 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t nat -D OUTPUT' failed: iptables: Bad rule (does a matching rule exist in that chain?).
2020-02-15 23:35:17 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -X DOCKER' failed: iptables: Too many links.
2020-02-15 23:35:17 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -X DOCKER-ISOLATION-STAGE-1' failed: iptables: Too many links.
2020-02-15 23:35:17 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -F DOCKER-ISOLATION' failed: iptables: No chain/target/match by that name.
2020-02-15 23:35:17 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -X DOCKER-ISOLATION' failed: iptables: No chain/target/match by that name.
2020-02-15 23:35:17 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -D FORWARD -i docker0 -o docker0 -j DROP' failed: iptables: Bad rule (does a matching rule exist in that chain?).
2020-02-15 23:35:18 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -D FORWARD -i docker0 -o docker0 -j DROP' failed: iptables: Bad rule (does a matching rule exist in that chain?).
2020-02-16 00:04:41 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -D FORWARD -i docker0 -o docker0 -j DROP' failed: iptables: Bad rule (does a matching rule exist in that chain?).
2020-02-16 00:04:41 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -D FORWARD -i docker0 -o docker0 -j DROP' failed: iptables: Bad rule (does a matching rule exist in that chain?).
2020-02-16 00:08:03 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -D FORWARD -i docker0 -o docker0 -j DROP' failed: iptables: Bad rule (does a matching rule exist in that chain?).
2020-02-16 00:08:03 WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -D FORWARD -i docker0 -o docker0 -j DROP' failed: iptables: Bad rule (does a matching rule exist in that chain?).

I cannot modify the DNS server globally on my server because I use a DNS service with custom internal domains, although my DNS service still works well, it is KVM.

Everything indicates that there must be a bug in the docker DNS query connector and not the system or system DNS configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
You can’t perform that action at this time.