Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 192.168.65.1:53: no such host

Question

I am new to dockers. When I am running the docker pull sonarqube I am getting the following error.

Error response from daemon: Get https://registry-1.docker.io/v2/: dial TCP: lookup registry-1.docker.io on 192.168.65.1:53: no such host

Can you please let me know why I am getting the error and how can I rectify this.

`192.168.0.0/16` is reserved, local IP space and https://registry-1.docker.io should not be pointing to it; what happens when you ping `registry-1.docker.io` ? — TJ Biddle, Nov 30 '17 at 18:49
I would suggest you to change DNS to 8.8.8.8. But it may not solve the problem in some cases. — Fony Lew, Feb 16 '18 at 04:16
I tried a few times the same command and it worked eventually. I did nothing. It's like the host has limited slots to serve and I had to be lucky or something. — LovaBill, Nov 15 '21 at 11:38
the Given IP implements that you are inside a Virtualmachine, I think the Problem is really that you have no Internet Connection. Check your Networkports for the VM, you need a NAT Port to be connected to the Internet. All given Answers are right actually but I guess this case Is realy about a missing Port — SamPhoenix, Mar 24 '22 at 08:03

score 113 · Answer 1 · answered Aug 25 '18 at 11:33

113

I had similar issue on Ubuntu 16.04 and manage to solve it by adding more nameservers

You can try too.

Open config file sudo nano /etc/resolv.conf and add the following under existing nameservers

nameserver 8.8.8.8

nameserver 8.8.4.4
run following commands to restart daemon and docker service

sudo systemctl daemon-reload

sudo systemctl restart docker

Now try to pull image you want docker pull sonarqube

answered Aug 25 '18 at 11:33

lev09

2,020
1
15
16

Consider this as the correct answer. Solved only with this. – Magno C Sep 02 '19 at 22:01
1

simply following step 2 worked for me – MoralCode Apr 23 '22 at 18:10

score 36 · Answer 2 · answered Sep 19 '18 at 13:52

36

In my case on a Mac, only a restart of the docker-machine did the work:

docker-machine restart

Uninstalling docker did not work! Just the above restart is enough!

answered Sep 19 '18 at 13:52

cyberPrivacy

907
10
19

2

This worked for me as well using windows docker toolbox – AndraeRay Dec 13 '19 at 08:24
1

Same here. Just restart fixed my issue – Jim C Mar 03 '20 at 19:21
Docker machine shouldn't really be used anymore – OneCricketeer Dec 31 '22 at 16:03

score 36 · Answer 3 · edited Jan 27 '21 at 15:00

36

I was able to resolve by running the below command.

sudo systemctl restart docker

edited Jan 27 '21 at 15:00

Tomer Shetah

8,413
7
27
35

answered Jan 27 '21 at 14:31

Jagadeeswar

537
1
7
9

In Windows 10 restarting Docker through the GUI was enough; I didn't need to run any command through the WSL2 terminal – Rafael Atías Apr 21 '23 at 12:01

score 14 · Answer 4 · edited Apr 20 '19 at 08:21

14

sudo vi /etc/resolv.conf

And change nameserver to 8.8.8.8

edited Apr 20 '19 at 08:21

Antoine Thiry

2,362
4
28
42

answered Apr 20 '19 at 06:12

Nitin

541
4
5

score 10 · Answer 5 · answered Jan 10 '20 at 06:22

10

I had the same issue, for me I was behind my office proxy and docker was not picking up the proxy set for terminal. To fix this, i have to set the proxy in docker settings window, which can be accessed from

task bar -> docker -> settings

answered Jan 10 '20 at 06:22

vikash vik

686
5
10

score 9 · Answer 6 · answered Dec 09 '20 at 23:19

9

I was able to solve this issue, by logging into docker.

sudo docker login
Enter your login credentials 
sudo docker pull 'yourImageName'

answered Dec 09 '20 at 23:19

Aishwarya Patil

447
5
9

1

How would this fix network resolution issue? – OneCricketeer Dec 31 '22 at 16:04

score 5 · Answer 7 · answered Apr 16 '21 at 21:25

5

in windows, just restart the docker, it worked for me. Go to Docker Desktop dashboard, click on the icon with setting icon and click restart

answered Apr 16 '21 at 21:25

Tushar Seth

563
7
15

score 4 · Answer 8 · answered Feb 14 '20 at 10:41

4

You need to add to your /etc/hosts in terminal write

$ sudo nano /etc/hosts

add below line and save it, try to run command and it will be working

34.228.211.243  registry-1.docker.io

answered Feb 14 '20 at 10:41

Shajed

647
10
14

score 4 · Answer 9 · answered Feb 21 '20 at 02:03

4

I just restarted and it works fine again!

answered Feb 21 '20 at 02:03

Micael Mota

433
3
7

Dennis Van Bets · Answer 10 · 2021-12-28T20:45:19.973

This could also be a DNS issue. Altering your nameservers will most likely resolve it, if is indeed related to your DNS.

You can verify the issue with: curl -vvv https://registry-1.docker.io/v2/ for a more detailed path.

If you are on ubuntu 18.04 or higher /etc/resolve.conf won't do the trick, they moved network management to NetPlan configs.

Add the google nameservers to your configuration (8.8.8.8 and 8.8.4.4)

find your network adapter name with ip a

network:
  version: 2
  renderer: NetworkManager
  ethernets:
      [network adapter name]:
              addresses: ...
              gateway4: ...
              nameservers:
                      addresses:
                              - 8.8.8.8
                              - 8.8.4.4
                      search: []

And run sudo netplan apply

score 4 · Answer 11 · answered Jun 06 '21 at 06:03

4

Disable experiment features and try again does the trick. Otherwise add the config below to daemon.json

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

answered Jun 06 '21 at 06:03

ZenithS

987
8
20

This response lacks the full file path, structure, and info about having to restart the docker service afterward. So, go to `/etc/docker/daemon.json`, edit the file with admin privileges, add this entry, remember about surrounding braces `{}` since it's a json file, save and then run `sudo systemctl restart docker` – Yourin Mar 04 '22 at 19:30

score 3 · Answer 12 · answered Oct 23 '18 at 08:06

If your machine are located within the Great China area or using related Virtual Server, add Registry Mirrors to help your bypass the complex network router.

Or your can set a http_proxy for your docker configuration, referencing this link: https://docs.docker.com/config/daemon/systemd/#httphttps-proxy

score 3 · Answer 13 · edited Dec 31 '22 at 16:06

3

make sure that your server is not located in the following areas:

Docker is a US company, we must comply with US export control regulations. In an effort to comply with these, we now block all IP addresses that are located in Cuba, Iran, North Korea, Republic of Crimea, Sudan, and Syria.

edited Dec 31 '22 at 16:06

OneCricketeer

179,855
19
132
245

answered Jun 01 '20 at 15:50

Ali_Hr

4,017
3
27
34

Please provide source of quote – OneCricketeer Dec 31 '22 at 16:05

score 2 · Answer 14 · edited Dec 31 '22 at 16:06

2

Things that might work:

Check your proxy settings
Restart docker
Go to your docker settings and check if you're signed in to docker hub, if you aren't, sign in and try again (This worked for me)

edited Dec 31 '22 at 16:06

OneCricketeer

179,855
19
132
245

answered May 18 '20 at 06:02

Mehr Heer

31
4

score 2 · Answer 15 · answered Oct 26 '20 at 14:19

2

It happens when you are not logged in too, it happened to me. Problem gone after I logged in

answered Oct 26 '20 at 14:19

Abdullah Ahçı

786
10
19

1

Logged in to what? How? – OneCricketeer Dec 31 '22 at 16:05
To Docker of course – Abdullah Ahçı Jan 03 '23 at 13:04
Docker hub? Amazon / Google / Github Docker Registry? Your own registry? – OneCricketeer Jan 03 '23 at 15:06
When It happened to me, I fixed it with loginning via Docker Desktop, Command line was giving that error when I was trying to pull without login – Abdullah Ahçı Jan 10 '23 at 14:08

score 1 · Answer 16 · answered Feb 04 '22 at 10:31

1

A restart of your internet connection might solve this.

answered Feb 04 '22 at 10:31

Chris Athanasiadis

330
3
13

1

Don't know why it got a downvote. In my case, I got this error when the internet connection was disconnected. Worked fine, after reconnecting. Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io on ***.***.**.*:**: no such host – ahairshi Feb 07 '22 at 06:42

score 0 · Answer 17 · answered May 17 '19 at 03:14

0

In China, Add 114.114.114.114 to resolv.conf fixed it. sudo echo "nameserver 114.114.114.114" >> /etc/resolv.conf

answered May 17 '19 at 03:14

Contropist

401
4
9

score 0 · Answer 18 · answered May 25 '20 at 13:28

0

Had same issue, I restarted docker and it worked

answered May 25 '20 at 13:28

Martin Karari

180
2
9

score 0 · Answer 19 · answered Apr 27 '21 at 14:38

I got the same error & I solved it by executing the below-mentioned commands, If you are working on the windows version, you can try these commands Steps to be followed : Open the command prompt & execute these commands,

set http_proxy="http://user:pwd@proxyurl.com:port"

set https_proxy="https://user:pwd@proxy-url.com:port"

score 0 · Answer 20 · answered May 17 '22 at 08:35

My issue was tha ti was behind a corporate proxy and hence i was unable to reach the registry-1.docker.io.

Solution:

I bypassed this URL registry-1.docker.io in the proxy server for following

SSL bypass
Authentication Bypass.

Then i configured the proxy settings in docker.service file in RHEL server as

Environment="HTTP_PROXY=http://proxy.example.com:80"
Environment="HTTPS_PROXY=http://proxy.example.com:443"
NO_PROXY=“tnd-harbor.india.airtel.itm,10.241.99.232,
registry-1.docker.io/v2/”

Make sure the HTTPS_PROXY protocol is http.

By doing this i was able to fetch images.

score 0 · Answer 21 · answered Mar 28 '23 at 01:15

0

After trying most solutions mentioned on this page nothing worked for me. Weirdly mine worked after updating docker desktop from some 4.16.x to 4.17.1 That update restarted docker and might've fixed whatever the issue was. Hope it helps someone.

answered Mar 28 '23 at 01:15

Hari

219
4
8

score 0 · Answer 22 · answered Apr 13 '23 at 14:12

For me the issue was due to eval $(minikube docker-env) in my terminal .bash_profile/.profile

When this runs it sets

export DOCKER_HOST="tcp://192.168.64.4:2376"

To fix I ran

unset DOCKER_HOST

I also removed eval $(minikube docker-env) from my shell env.

score 0 · Answer 23 · answered Apr 27 '23 at 07:38

I had this issue and tried so many solutions like restarting-docker, setting buildkit to false in docker-Engine setting tab (Docker Windows), etc, all to no avail. When I viewed my containers and images in Docker-window, the list were empty.

I re-installed docker and everything was fine.

score 0 · Answer 24 · answered May 21 '23 at 15:08

0

In My case the issue was resolved by changing the DNS settings Wi-Fi network.

By modifying the DNS server to 8.8.8.8 (Google Public DNS) from 192.168.1.1 it worked

answered May 21 '23 at 15:08

Santosh Joshi

3,290
5
36
49

score -1 · Answer 25 · answered Jul 10 '19 at 07:10

-1

I was getting the same error. Tried a few things like restarting the server, checking configuration etc... Finally, it got resolved by adding proxies (since I was using it inside my organization network)

answered Jul 10 '19 at 07:10

ShailendraChoudhary

143
1
3
10

1

How did you add proxies – Gunjan Khandelwal Jul 20 '22 at 01:13

score -1 · Answer 26 · answered Dec 20 '21 at 12:23

-1

I had the same problem, for me it was ACR repository name that I have misspelled. Maybe check your variables. I used it within Github Actions in the secret sections.

answered Dec 20 '21 at 12:23

Marc Ottenbacher

144
2
13

score -1 · Answer 27 · answered Jan 25 '22 at 19:38

-1

I had this same issue with a different solution. The issue was that the internet wasn't connected. That's another thing to check if none of these fix it for you!

answered Jan 25 '22 at 19:38

My Code Made Me Suicidal

514
1
6
20

Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 192.168.65.1:53: no such host

27 Answers27

Linked