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 · 79 comments

Comments

Projects
None yet
@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.

Show comment
Hide comment
@LevonBecker

LevonBecker 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

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.

Show comment
Hide comment
@ijc

ijc Feb 22, 2017

Contributor

@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.

Contributor

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.

Show comment
Hide comment
@nabedge

nabedge Feb 22, 2017

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

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.

Show comment
Hide comment
@LevonBecker

LevonBecker commented Feb 22, 2017

sure thing

@nicksnyder

This comment has been minimized.

Show comment
Hide comment
@nicksnyder

nicksnyder Feb 28, 2017

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

nicksnyder commented Feb 28, 2017

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

@rainder

This comment has been minimized.

Show comment
Hide comment
@rainder

rainder Feb 28, 2017

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

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.

Show comment
Hide comment
@ferbass

ferbass Feb 28, 2017

same problem after reinstall
Fixed when switching to beta version

ferbass commented Feb 28, 2017

same problem after reinstall
Fixed when switching to beta version

@LevonBecker

This comment has been minimized.

Show comment
Hide comment
@LevonBecker

LevonBecker Feb 28, 2017

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

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.

Show comment
Hide comment
@rainder

rainder Feb 28, 2017

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

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.

Show comment
Hide comment
@LevonBecker

LevonBecker 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

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.

Show comment
Hide comment
@MagnusS

MagnusS Mar 8, 2017

Member

@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!

Member

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.

Show comment
Hide comment
@ferbass

ferbass 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

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.

Show comment
Hide comment
@MikhailKaduchka

MikhailKaduchka Mar 9, 2017

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

change nameserver to 8.8.8.8

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.

Show comment
Hide comment
@richarda23

richarda23 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!

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.

Show comment
Hide comment
@ranaskr

ranaskr 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

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.

Show comment
Hide comment
@pnowy

pnowy Apr 16, 2017

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

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.

Show comment
Hide comment
@carusology

carusology 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" ]}

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.

Show comment
Hide comment
@umbruch

umbruch 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

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.

Show comment
Hide comment
@zatamine

zatamine May 25, 2017

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

zatamine commented May 25, 2017

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

@akki0996

This comment has been minimized.

Show comment
Hide comment
@akki0996

akki0996 Jul 5, 2017

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

akki0996 commented Jul 5, 2017

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

@omerlh

This comment has been minimized.

Show comment
Hide comment
@omerlh

omerlh Jul 9, 2017

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

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.

Show comment
Hide comment
@lpcardinal

lpcardinal Jul 13, 2017

Re-installed docker and now it work.

lpcardinal commented Jul 13, 2017

Re-installed docker and now it work.

@azamatsulaiman

This comment has been minimized.

Show comment
Hide comment
@azamatsulaiman

azamatsulaiman Jul 14, 2017

solved restarting docker from settings (windows 10)

azamatsulaiman commented Jul 14, 2017

solved restarting docker from settings (windows 10)

@veeshall

This comment has been minimized.

Show comment
Hide comment
@veeshall

veeshall 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

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.

Show comment
Hide comment
@samsonkolge

samsonkolge Aug 3, 2017

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

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.

Show comment
Hide comment
@kethansrinivas9

kethansrinivas9 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$

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$

@MohsenBzm

This comment has been minimized.

Show comment
Hide comment
@MohsenBzm

MohsenBzm Dec 26, 2017

Restarting to factory settings worked for me.

MohsenBzm commented Dec 26, 2017

Restarting to factory settings worked for me.

@astanciu

This comment has been minimized.

Show comment
Hide comment
@astanciu

astanciu Dec 28, 2017

Also running into this. Resetting to factory works but as soon as I run docker-compose up, it breaks to this error again.

UPDATE: Figured out the problem for me.... my docker settings for subnet was set to "10.0.0.0/24" and my docker-compose.yaml file also created a network using the same subnet. Changing the subnet in my yaml file fixed it. (deleting the network actually fixes it)

astanciu commented Dec 28, 2017

Also running into this. Resetting to factory works but as soon as I run docker-compose up, it breaks to this error again.

UPDATE: Figured out the problem for me.... my docker settings for subnet was set to "10.0.0.0/24" and my docker-compose.yaml file also created a network using the same subnet. Changing the subnet in my yaml file fixed it. (deleting the network actually fixes it)

@ganeshkondal

This comment has been minimized.

Show comment
Hide comment
@ganeshkondal

ganeshkondal Jan 14, 2018

I am in Mac Sierra. 8.8.8.8 DNS entry didn't work. I am not behind a proxy.

Only after doing a factory reset, I got out of the error.

ganeshkondal commented Jan 14, 2018

I am in Mac Sierra. 8.8.8.8 DNS entry didn't work. I am not behind a proxy.

Only after doing a factory reset, I got out of the error.

@FX-HAO

This comment has been minimized.

Show comment
Hide comment
@FX-HAO

FX-HAO Jan 22, 2018

Get the same issue on macOS. I am using proxy. I configured the proxy server to http://192.168.65.1:1087. It did work perfectly. Setting DNS to 8.8.8.8 and 8.8.4.4 does not fix it. Dokcer version 17.12.0-ce.

FX-HAO commented Jan 22, 2018

Get the same issue on macOS. I am using proxy. I configured the proxy server to http://192.168.65.1:1087. It did work perfectly. Setting DNS to 8.8.8.8 and 8.8.4.4 does not fix it. Dokcer version 17.12.0-ce.

@tnovau

This comment has been minimized.

Show comment
Hide comment
@tnovau

tnovau Feb 1, 2018

Setting DNS to 8.8.8.8 and 8.8.4.4 fix the problem for me in Windows 10.

tnovau commented Feb 1, 2018

Setting DNS to 8.8.8.8 and 8.8.4.4 fix the problem for me in Windows 10.

@snehabarshamishra

This comment has been minimized.

Show comment
Hide comment
@snehabarshamishra

snehabarshamishra Feb 16, 2018

Worked for me as:

  1. kubectl get service -n kube-system > Take the ClusterIP from the output.
  2. Take the IP and put it as nameserver in /etc/resolve.conf
  3. exit
  4. eval $(minikube docker-env)

snehabarshamishra commented Feb 16, 2018

Worked for me as:

  1. kubectl get service -n kube-system > Take the ClusterIP from the output.
  2. Take the IP and put it as nameserver in /etc/resolve.conf
  3. exit
  4. eval $(minikube docker-env)
@harry-chin

This comment has been minimized.

Show comment
Hide comment
@harry-chin

harry-chin Feb 21, 2018

On my Mac high Sierra with docker 17.12.0-ce

docker->Preference->Reset (bomb icon on right-up side) -> Reset to factory defaults is only worked for me.

harry-chin commented Feb 21, 2018

On my Mac high Sierra with docker 17.12.0-ce

docker->Preference->Reset (bomb icon on right-up side) -> Reset to factory defaults is only worked for me.

@EugeneLugin

This comment has been minimized.

Show comment
Hide comment
@EugeneLugin

EugeneLugin Feb 22, 2018

win 8.1
docker toolbox 18.01
I had same issue till I set 8.8.8.8 as dns

EugeneLugin commented Feb 22, 2018

win 8.1
docker toolbox 18.01
I had same issue till I set 8.8.8.8 as dns

@fabianskii

This comment has been minimized.

Show comment
Hide comment
@fabianskii

fabianskii Mar 3, 2018

win10 same issue, reset to docker factory defaults fixed it.

fabianskii commented Mar 3, 2018

win10 same issue, reset to docker factory defaults fixed it.

@germanp

This comment has been minimized.

Show comment
Hide comment
@germanp

germanp Mar 15, 2018

I had the same issue on linux. I've restarted the docker service and it got solved. Before having this issue I was using a crappy cell phone connection to pull some images, so maybe it is related. So I changed to a wifi connection and restarted the daemon.

germanp commented Mar 15, 2018

I had the same issue on linux. I've restarted the docker service and it got solved. Before having this issue I was using a crappy cell phone connection to pull some images, so maybe it is related. So I changed to a wifi connection and restarted the daemon.

@FX-HAO

This comment has been minimized.

Show comment
Hide comment
@FX-HAO

FX-HAO Mar 27, 2018

Just tried the latest release version(18.03.0-ce-mac59). The "magic" IP(192.168.65.1) seems to be unnecessary. Now it's just localhost, it works.

FX-HAO commented Mar 27, 2018

Just tried the latest release version(18.03.0-ce-mac59). The "magic" IP(192.168.65.1) seems to be unnecessary. Now it's just localhost, it works.

@staticdreams

This comment has been minimized.

Show comment
Hide comment
@staticdreams

staticdreams Apr 8, 2018

I used the new 1.1.1.1 dns and it fixed my issue

staticdreams commented Apr 8, 2018

I used the new 1.1.1.1 dns and it fixed my issue

@MikhailTymchukDX

This comment has been minimized.

Show comment
Hide comment
@MikhailTymchukDX

MikhailTymchukDX Apr 22, 2018

I worked around this by I referring to insecure registry by IP instead of symbolic name.

MikhailTymchukDX commented Apr 22, 2018

I worked around this by I referring to insecure registry by IP instead of symbolic name.

@IzaGz

This comment has been minimized.

Show comment
Hide comment
@IzaGz

IzaGz Apr 26, 2018

@MikhailKaduchka after restarting the docker-machine previous IP returned
search mshome.net nameserver 10.0.2.3
does not help

IzaGz commented Apr 26, 2018

@MikhailKaduchka after restarting the docker-machine previous IP returned
search mshome.net nameserver 10.0.2.3
does not help

@IzaGz

This comment has been minimized.

Show comment
Hide comment
@IzaGz

IzaGz Apr 26, 2018

@harry-chin where can i find this Preferencies? i user docker-machine

IzaGz commented Apr 26, 2018

@harry-chin where can i find this Preferencies? i user docker-machine

@IzaGz

This comment has been minimized.

Show comment
Hide comment
@IzaGz

IzaGz Apr 26, 2018

@EugeneLugin have you fixed it?

IzaGz commented Apr 26, 2018

@EugeneLugin have you fixed it?

@harry-chin

This comment has been minimized.

Show comment
Hide comment
@harry-chin

harry-chin Apr 26, 2018

@IzaGz you can find the docker icon on the right up of the Mac screen around WiFi status icon. Click the docker icon then click Preferences. Or move docker app using Command+Tap, and then press Command+, It for Mac.

harry-chin commented Apr 26, 2018

@IzaGz you can find the docker icon on the right up of the Mac screen around WiFi status icon. Click the docker icon then click Preferences. Or move docker app using Command+Tap, and then press Command+, It for Mac.

@SadiqueManzar

This comment has been minimized.

Show comment
Hide comment
@SadiqueManzar

SadiqueManzar May 29, 2018

Having same issue, installed docker but failing the below docker build command

docker build --ulimit nofile=65535:65535 --ulimit nproc=25059:25059 -t esri/city_in_motion:0.1 .

Sending build context to Docker daemon 21.46 MB
Step 1/20 : FROM phusion/baseimage:0.10.1
Trying to pull repository registry.access.redhat.com/phusion/baseimage ...
Trying to pull repository docker.io/phusion/baseimage ...
Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 10.37.161.54:53: no such host

uname -r
3.10.0-862.el7.x86_64

docker version
Client:
Version: 1.13.1
API version: 1.26
Package version: docker-1.13.1-63.git94f4240.el7.x86_64
Go version: go1.9.2
Git commit: 94f4240/1.13.1
Built: Mon Apr 30 15:45:42 2018
OS/Arch: linux/amd64

Server:
Version: 1.13.1
API version: 1.26 (minimum version 1.12)
Package version: docker-1.13.1-63.git94f4240.el7.x86_64
Go version: go1.9.2
Git commit: 94f4240/1.13.1
Built: Mon Apr 30 15:45:42 2018
OS/Arch: linux/amd64
Experimental: false

docker info
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 0
Server Version: 1.13.1
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: journald
Cgroup Driver: systemd
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Authorization: rhel-push-plugin
Swarm: inactive
Runtimes: runc docker-runc
Default Runtime: docker-runc
Init Binary: /usr/libexec/docker/docker-init-current
containerd version: (expected: aa8187dbd3b7ad67d8e5e3a15115d3eef43a7ed1)
runc version: e9c345b3f906d5dc5e8100b05ce37073a811c74a (expected: 9df8b306d01f59d3a8029be411de015b7304dd8f)
init version: 5b117de7f824f3d3825737cf09581645abbe35d4 (expected: 949e6facb77383876aeff8a6944dde66b3089574)
Security Options:
seccomp
WARNING: You're not using the default seccomp profile
Profile: /etc/docker/seccomp.json
selinux
Kernel Version: 3.10.0-862.el7.x86_64
Operating System: Red Hat Enterprise Linux
OSType: linux
Architecture: x86_64
Number of Docker Hooks: 3
CPUs: 4
Total Memory: 11.57 GiB
Name: DX2821.etisalat.corp.ae
ID: YNDM:6SCW:HHDL:GNEJ:2L2J:5DL4:345L:SI4J:Z3JK:7NUZ:LN6W:2PBL
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://registry.access.redhat.com/v1/
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Registries: registry.access.redhat.com (secure), docker.io (secure)

Kindly help , how could i fix the above error.

SadiqueManzar commented May 29, 2018

Having same issue, installed docker but failing the below docker build command

docker build --ulimit nofile=65535:65535 --ulimit nproc=25059:25059 -t esri/city_in_motion:0.1 .

Sending build context to Docker daemon 21.46 MB
Step 1/20 : FROM phusion/baseimage:0.10.1
Trying to pull repository registry.access.redhat.com/phusion/baseimage ...
Trying to pull repository docker.io/phusion/baseimage ...
Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 10.37.161.54:53: no such host

uname -r
3.10.0-862.el7.x86_64

docker version
Client:
Version: 1.13.1
API version: 1.26
Package version: docker-1.13.1-63.git94f4240.el7.x86_64
Go version: go1.9.2
Git commit: 94f4240/1.13.1
Built: Mon Apr 30 15:45:42 2018
OS/Arch: linux/amd64

Server:
Version: 1.13.1
API version: 1.26 (minimum version 1.12)
Package version: docker-1.13.1-63.git94f4240.el7.x86_64
Go version: go1.9.2
Git commit: 94f4240/1.13.1
Built: Mon Apr 30 15:45:42 2018
OS/Arch: linux/amd64
Experimental: false

docker info
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 0
Server Version: 1.13.1
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: journald
Cgroup Driver: systemd
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Authorization: rhel-push-plugin
Swarm: inactive
Runtimes: runc docker-runc
Default Runtime: docker-runc
Init Binary: /usr/libexec/docker/docker-init-current
containerd version: (expected: aa8187dbd3b7ad67d8e5e3a15115d3eef43a7ed1)
runc version: e9c345b3f906d5dc5e8100b05ce37073a811c74a (expected: 9df8b306d01f59d3a8029be411de015b7304dd8f)
init version: 5b117de7f824f3d3825737cf09581645abbe35d4 (expected: 949e6facb77383876aeff8a6944dde66b3089574)
Security Options:
seccomp
WARNING: You're not using the default seccomp profile
Profile: /etc/docker/seccomp.json
selinux
Kernel Version: 3.10.0-862.el7.x86_64
Operating System: Red Hat Enterprise Linux
OSType: linux
Architecture: x86_64
Number of Docker Hooks: 3
CPUs: 4
Total Memory: 11.57 GiB
Name: DX2821.etisalat.corp.ae
ID: YNDM:6SCW:HHDL:GNEJ:2L2J:5DL4:345L:SI4J:Z3JK:7NUZ:LN6W:2PBL
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://registry.access.redhat.com/v1/
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Registries: registry.access.redhat.com (secure), docker.io (secure)

Kindly help , how could i fix the above error.

@IzaGz

This comment has been minimized.

Show comment
Hide comment
@IzaGz

IzaGz May 29, 2018

@harry-chin but what if i use docker-toolbox- i havent this icon. what should i do in this way?

IzaGz commented May 29, 2018

@harry-chin but what if i use docker-toolbox- i havent this icon. what should i do in this way?

@SadiqueManzar

This comment has been minimized.

Show comment
Hide comment
@SadiqueManzar

SadiqueManzar May 29, 2018

@IzaGz any solution for my above mentioned issue.

SadiqueManzar commented May 29, 2018

@IzaGz any solution for my above mentioned issue.

@guitong guitong referenced this issue Jun 20, 2018

Open

Docker #11

@HunderlineK

This comment has been minimized.

Show comment
Hide comment
@HunderlineK

HunderlineK Jun 21, 2018

I had this issue in windows 10 using gitbash; it was because gitbash doesn't map ports properly on windows. Use cmd, problem solved

HunderlineK commented Jun 21, 2018

I had this issue in windows 10 using gitbash; it was because gitbash doesn't map ports properly on windows. Use cmd, problem solved

@koji-2

This comment has been minimized.

Show comment
Hide comment
@koji-2

koji-2 Jul 31, 2018

I experienced this problem with Windows for Docker.

Environment

Client:
Version: 18.06.0-ce
API version: 1.38
Go version: go1.10.3
Git commit: 0ffa 825
Built: Wed Jul 18 19: 05: 28 8 2018
OS / Arch: windows / amd64
Experimental: false

Error message

PS C: \ WINDOWS \ system32> docker run hello-world
Unable to find image 'hello-world: latest' locally
Error response from daemon: Get https://registry-1.docker.io/v2/: proxyconnect tcp: dial tcp: lookup proxy on 192.168. 65.1: 53: no such host.
See 'C: \ Program Files \ Docker \ Docker \ Resources \ bin \ docker.exe run --help'.

Discussion

The proxy server had specified the host name. We thought that proxy server name resolution had failed.

Countermeasures

Web Server (HTTP :) proxyservername: 8080
Secure Web Server (HTTP :) proxyservername: 8080

To

Web Server (HTTP :) IP adoption: 8080
Secure Web Server (HTTP :) IP adoption: 8080

And solved it.

Everyone's post was a great hint. Thank you.

koji-2 commented Jul 31, 2018

I experienced this problem with Windows for Docker.

Environment

Client:
Version: 18.06.0-ce
API version: 1.38
Go version: go1.10.3
Git commit: 0ffa 825
Built: Wed Jul 18 19: 05: 28 8 2018
OS / Arch: windows / amd64
Experimental: false

Error message

PS C: \ WINDOWS \ system32> docker run hello-world
Unable to find image 'hello-world: latest' locally
Error response from daemon: Get https://registry-1.docker.io/v2/: proxyconnect tcp: dial tcp: lookup proxy on 192.168. 65.1: 53: no such host.
See 'C: \ Program Files \ Docker \ Docker \ Resources \ bin \ docker.exe run --help'.

Discussion

The proxy server had specified the host name. We thought that proxy server name resolution had failed.

Countermeasures

Web Server (HTTP :) proxyservername: 8080
Secure Web Server (HTTP :) proxyservername: 8080

To

Web Server (HTTP :) IP adoption: 8080
Secure Web Server (HTTP :) IP adoption: 8080

And solved it.

Everyone's post was a great hint. Thank you.

@iamnumlock

This comment has been minimized.

Show comment
Hide comment
@shailendra333

This comment has been minimized.

Show comment
Hide comment
@shailendra333

shailendra333 Aug 29, 2018

I faced same error too. Changing change nameserver to 8.8.8.8 solved. Thanks.

shailendra333 commented Aug 29, 2018

I faced same error too. Changing change nameserver to 8.8.8.8 solved. Thanks.

@cythb

This comment has been minimized.

Show comment
Hide comment
@cythb

cythb Sep 12, 2018

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

change nameserver to 8.8.8.8

fixed mine

cythb commented Sep 12, 2018

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

change nameserver to 8.8.8.8

fixed mine

@juliocarneiro

This comment has been minimized.

Show comment
Hide comment
@juliocarneiro

juliocarneiro Sep 12, 2018

set the mirror https://docker.mirrors.ustc.edu.cn worked for me! version 18.06.1-ce, build e68fc7a

juliocarneiro commented Sep 12, 2018

set the mirror https://docker.mirrors.ustc.edu.cn worked for me! version 18.06.1-ce, build e68fc7a

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment