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

nabedge commented 7 years ago

$ 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 ? https://github.com/docker/for-mac/issues/1025

LevonBecker commented 7 years ago

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 commented 7 years ago

@nabedge please use the :whale: menu :arrow_right: `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 commented 7 years ago

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

LevonBecker commented 7 years ago

sure thing

nicksnyder commented 7 years ago

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

rainder commented 7 years ago

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

ferbass commented 7 years ago

same problem after reinstall Fixed when switching to beta version

LevonBecker commented 7 years ago

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

rainder commented 7 years ago

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

LevonBecker commented 7 years ago

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 commented 7 years ago

@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 commented 7 years ago

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

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

MikhailKaduchka commented 7 years ago

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

change nameserver to 8.8.8.8

richarda23 commented 7 years ago

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 commented 7 years ago

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 commented 7 years ago

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

carusology commented 7 years ago

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 commented 7 years ago

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 commented 7 years ago

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

akki0996 commented 7 years ago

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

omerlh commented 7 years ago

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

lpcardinal commented 7 years ago

Re-installed docker and now it work.

azamatsulaiman commented 7 years ago

solved restarting docker from settings (windows 10)

veeshall commented 7 years ago

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 commented 7 years ago

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

kethansrinivas9 commented 7 years ago

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$

MTWiley commented 7 years ago

Win 10 Machine - Restarting docker fixed it for me

jtough-github commented 7 years ago

Windows 10 - Restarting docker fixed the problem

GopalSingh07 commented 7 years ago

Same problem it solved after re-installed same version but before we should uninstall all like virtual box and should be deleted .docker from C:user/username/.docker after uninstalling restart system then install once again it will work

parand87 commented 7 years ago

change nameserver to 8.8.8.8 worked for me too

BiscoWeb commented 7 years ago

Resetting the docker for mac solved the issue, Its under preferences,

k-v-no1 commented 7 years ago

Doing a System/VM reboot worked for me.

karthik-padav commented 7 years ago

Reinstall fixed this problem for me

kostyanius commented 7 years ago

reeinstall did not solve an issue. 17.07 version of docker. using 5005 port for registry in my gitlab.yml

bliaxiong commented 7 years ago

Super weird, my /etc/resolve.conf was 8.8.8.8. I changed it to 8.8.4.4 and it worked.

sidduSthawarmath commented 7 years ago

I have added nameserver 8.8.4.4 in /etc/resolve.conf file and it worked for me

jerome-arzel commented 7 years ago

This problem occurs when the network is down, specifically when the dns server did not respond.

antonszilasi commented 7 years ago

restarted the docker-machine solved the problem for me

laytoneverson commented 6 years ago

I'm running into troubles with dns resolution. I was able to resolve it once by switching the dns from 8.8.8.8 to the automatic setting. It has only been a few hours now and I'm running into resolution problems again.

A diagnostic was uploaded with id: 2E28A919-AEC5-4465-BCB2-947BFD956A67/2017-10-22_04-20-19

Here are the error messages I get at the cli:

host$ docker-compose exec workspace bash
root@c190ce7f5d52:/var/www# composer create-project sylius/sylius-standard acme

Do not run Composer as root/super user! See https://getcomposer.org/root for details. 
The "https://packagist.org/packages.json" file could not be downloaded: php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution 
failed to open stream: php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution https://packagist.org could not be fully loaded, package information was loaded from the local cache and may be out of date

  [Composer\Downloader\TransportException]
  The "http://packagist.org/p/sylius/sylius-standard%246ed7457d36c3c529786da191dbb431aea34fed81e1ce49225683223ce787de66.json" file could not be downloaded: php_network 
  _getaddresses: getaddrinfo failed: Temporary failure in name resolution
 failed to open stream: php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution

Problems outside a container:

C:\..\Projects\laradock [master ≡ +0 ~4 -0 !]
$ docker run busybox ping -c 1 192.203.230.10
Unable to find image 'busybox:latest' locally                                                                                                                             
C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:59044->[::1]:53: read: connection refused.
See 'C:\Program Files\Docker\Docker\Resources\bin\docker.exe run --help'

C:\..\Projects\laradock [master ≡ +0 ~4 -0 !]                                                                                                         
$  docker pull busybox
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]:36936->[::1]:53: read: connection refused
C:\..\Projects\laradock [master ≡ +0 ~4 -0 !]                                                                                                                    
$

NaitikShah commented 6 years ago

export DOCKER_HOST= OR unset DOCKER_HOST

Source:

I simply ran this command and everything worked back to normal

dkcwd commented 6 years ago

Like @antonszilasi mentioned, restarting the docker machine could help if there is a network issue. It worked for me.

If your docker machine name is default:

eval $(docker-machine env default)
docker-machine restart default

You should see something like:

(default) Check network to re-create if needed...
(default) Waiting for an IP...
Waiting for SSH to be available...
Detecting the provisioner...
Restarted machines may have new IP addresses. You may need to re-run the `docker-machine env` command.

So then you can:

eval $(docker-machine env default)

and try again.

VaverDariush commented 6 years ago

Setting docker's Settings->Network->DNS Server to fixed 8.8.8.8 helped me solve this issue in Win10

guthyerrz commented 6 years ago

My problem was that I had Charles configured at one point, and when I was trying to do execute a docker pull the Charles application was closed, and for some reason the Docker did not reset the proxy settings. So When I opened Charles again everything worked fine

aidapsibr commented 6 years ago

My problem was I connected, and then disconnected to a VPN while Docker was running, so it had stale DNS settings.

Stark-X commented 6 years ago

In my case, I just using the command systemctl restart dnsmasq to restart the "DNS caching server", then resumed. Or, you could just stop it with systemctl stop dnsmasq .