docker: Error response from daemon: Get https://registry-1.docker.io/v2/: Service Unavailable. IN DOCKER , MAC

Question

I am having this issue

system3:postgres saurabh-gupta2$ docker build -t postgres .
Sending build context to Docker daemon  38.91kB
Step 1/51 : FROM registry.access.redhat.com/rhel7/rhel
Get https://registry.access.redhat.com/v2/: Service Unavailable

docker run  -t apline 
Unable to find image 'apline:latest' locally
docker: Error response from daemon: Get https://registry-1.docker.io/v2/: Service Unavailable.
See 'docker run --help'.

I have looked for a solution that says to set proxy, but I have set the proxy for the wifi.

https://docs.docker.com/docker-for-mac/networking/#httphttps-proxy-support

Still, it is not working.

I have set proxy for docker too. It is not working.

in Preference -> proxies

Docker version 17.12 ce

I also want to know if the proxy is the issue then how can I check it is set, what is work around for this?

Ubuntu uses systemd for the docker. After following the steps in the link below things worked for me and I could successfully run docker pull mysql with no access denied error from the docker registry https://docs.docker.com/config/daemon/systemd/ Senthil — Senthil Ganesan, Jun 03 '19 at 00:25
Does https://registry-1.docker.io/v2/ require that you be logged in within Docker desktop? — djangofan, Jan 20 '21 at 19:09
Have you tried logging in with docker desktop? I had this issue and logging in with docker desktop solved it — Ali Mert Çakar, Aug 02 '21 at 07:52

kenorb · Answer 1 · 2019-01-05T16:54:13.290

53

Here are few suggestions:

Try restarting your Docker service.

Check your network connections. For example by the following shell commands:

</dev/tcp/registry-1.docker.io/443 && echo Works || echo Problem
curl https://registry-1.docker.io/v2/ && echo Works || echo Problem

Check your proxy settings (e.g. in /etc/default/docker).

If above won't help, this could be a temporary issue with the Docker services (as per Service Unavailable).

^{Related: GH-842 - 503 Service Unavailable at http://hub.docker.com.}

I had this problem for past days, it just worked after that.

You can consider raising the issue at docker/hub-feedback repo, check at, Docker Community Forums, or contact Docker Support directly.

edited Jan 05 '19 at 16:54

answered Apr 26 '18 at 12:26

kenorb

155,785
88
678
743

2

For those running docker toolbox, shutting down the virtual box and then running the "Docker quickstart terminal" resolved it for me. Maybe there's a better way to restart it, but that worked. – JohnnyFun Jan 27 '19 at 14:57
This doesn't seem to work with recent Docker / Ubuntu (18.09, 18.04). I needed to update [systemd-config](https://docs.docker.com/config/daemon/systemd/) – Enno Gröper Apr 29 '19 at 12:35
3

To restart docker was the solution for me. Thanks. – Alexandru Burca Apr 03 '21 at 20:09
no solution worked for me then I restarted my computer and bingo. – Rafiq Apr 15 '21 at 18:10
#1 worked for me. I had checked /etc/default/docker which had an old password. Updated it. Still didnt work. Restarted docker. $ sudo service docker restart And it started working. – Chai Ang Nov 29 '22 at 01:06

score 30 · Answer 2 · answered Jul 02 '20 at 11:49

30

docker logout
docker login

This might solve your problem

answered Jul 02 '20 at 11:49

DevSay

886
1
14
32

I had to login with another personal access-token – Rafael Guimarães Jun 14 '22 at 21:06

score 19 · Answer 3 · answered Dec 03 '18 at 01:16

I tried running on Windows, and got this problem after an update. I tried restarting the docker service as well as my pc, but nothing worked.

When running:

curl https://registry-1.docker.io/v2/ && echo Works

I got back:

{"errors":[{"code":"UNAUTHORIZED","message":"authentication required","detail":null}]}
Works

Eventually, I tried: https://github.com/moby/moby/issues/22635#issuecomment-284956961

By changing the fixed address to 8.8.8.8:

Which worked for me! I still got the unauthorized message for curl https://registry-1.docker.io/v2/ but I managed to pull images from docker hub.

score 13 · Answer 4 · edited Nov 25 '20 at 17:39

13

For me I had this issue when I first installed Docker and ran

docker run hello-world

I got an authentication required error when I ran

curl https://registry-1.docker.io/v2/ && echo Works

All I needed to do was to restart my MacOS and then run the command again, it just started pulling the image and i got the message

Hello from Docker!
This message shows that your installation appears to be working correctly.

edited Nov 25 '20 at 17:39

Scott Stensland

26,870
12
93
104

answered Oct 30 '18 at 16:39

Oluwatobi Omotayo

1,719
14
28

I had the same behavior on a virtual machine with centos (hosted on windows 10). Restarting the vm solved the issue. – A. Wolf Nov 24 '20 at 07:05

Diego Turiso · Answer 5 · 2019-10-08T07:41:59.083

It's clearly a proxy issue: docker proxies https connections to the wrong place. Bear in mind that docker proxy settings may be different from the operating system (and curl) ones. Here's how I managed to solve the issue:

First of all, find out where are you proxying your docker https requests:

# docker info | grep Proxy
Http Proxy: http://<my.proxy.server>:8080
Https Proxy: https://<my.proxy.server>:8080
No Proxy: localhost,127.0.0.1

and double check your https settings.

In my case, I realized that the "Https proxy" was set to https://... instead of http://..., so I corrected it in /etc/sysconfig/docker file (I'm using RHEL7) and, after a docker restart with:

# systemctl restart docker

the proxy variable shows up succesfully updated:

# docker info | grep Proxy
Http Proxy: http://<my.proxy.server>:8080
Https Proxy: http://<my.proxy.server>:8080
No Proxy: localhost,127.0.0.1

and everything works fine :-)

Man ive been troubleshooting this for hours! This fixed it for me. Modified proxy settings and it worked like a charm...I had a custom proxy server running on my lan for testing. — Freddy, Apr 17 '22 at 18:02

score 5 · Answer 6 · answered Aug 26 '19 at 04:49

5

One option which worked for me on MAC.

Click on the Docker Icon in the tray. Open Preferences -> Proxies. Click on Manual Proxy and specify Web Server (HTTP) proxy and Secure Web server (HTTPS) proxy in the same format as we specify in HTTPS_PROXY env variable. Choose Apply and Restart.

This Worked for me

answered Aug 26 '19 at 04:49

Ranganath D

59
1
1

1

dude this is very vague! I didn't get what should i add in Web server proxy and secure webserver – Ahmed Khashaba Dec 14 '21 at 09:12
For me worked perfectly! thanks! Basically is follow exactly what he said. If you are behind a proxy, take the value from doing "echo $http_proxy" in your terminal and use it where he says. – Eric Mar 06 '23 at 17:00

score 4 · Answer 7 · answered Feb 27 '19 at 19:34

4

Just to add, in case anyone else comes across this issue.

On a Mac I had to logout and log back in.

docker logout

docker login

Then it prompts for username (NOTE: Not email) and password. (Need an account on https://hub.docker.com to pull images down)

Then it worked for me.

answered Feb 27 '19 at 19:34

Brian

498
6
11

I get the same problem when logging in? – Peter Feb 02 '21 at 07:18

score 4 · Answer 8 · 2019-03-01T12:48:38.473

NTML PROXY AND DOCKER 

If your company is behind MS Proxy Server that using the proprietary NTLM protocol.

You need to install **Cntlm** Authentication Proxy

After this SET the proxy in 
/etc/systemd/system/docker.service.d/http-proxy.conf) with the following format:

[Service]

Environment=“HTTP_PROXY=http://<<IP OF CNTLM Proxy Server>>:3182”

In addition you can set in the .DockerFile
export http_proxy=http://<<IP OF CNTLM Proxy Server>>:3182
export https_proxy=http://<IP OF CNTLM Proxy Server>>:3182
export no_proxy=localhost,127.0.0.1,10.0.2.*

Followed by:
systemctl daemon-reload

systemctl restart docker

This Worked for me

I did not had to install Cntlm, setting the proxy in /etc/systemd/system/docker.service.d/http-proxy.conf was enough — miszczu, May 17 '19 at 09:26

score 4 · Answer 9 · answered Jul 01 '19 at 11:01

4

For me the problem was solved by restarting the docker daemon:

sudo systemctl restart docker

answered Jul 01 '19 at 11:01

Mostafa Talebi

8,825
16
61
105

score 3 · Answer 10 · edited Nov 25 '20 at 17:40

3

try to reload daemon then restart docker service.

systemctl daemon-reload

edited Nov 25 '20 at 17:40

Scott Stensland

26,870
12
93
104

answered Feb 14 '19 at 09:43

Apriliansyah Idris

31
2

score 3 · Answer 11 · edited May 30 '21 at 02:26

3

Recheck Proxy Settings with the following commands

docker info | grep Proxy
Check VPN Connectivity
If VPN not using CHECK NET connectivity
Reinstall Docker and repeat the above steps.
Enjoy

edited May 30 '21 at 02:26

Sabito stands with Ukraine

4,271
8
34
56

answered Oct 26 '20 at 12:04

Vineet Kumar

333
4
7

score 3 · Answer 12 · answered Feb 16 '21 at 15:58

I had this same issue when working on an Ubuntu server.

I was getting the following error:

deploy@my-comp:~$ docker login -u my-username -p my-password
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp 35.175.83.85:443: connect: connection refused

Here are the things I tried that did not work:

Restarting the docker service using sudo docker systemctl restart docker
Powering off and restarting the Ubuntu server.
Changing the name server to 8.8.8.8 in the /etc/resolv.conf file

Here's what worked for me:

I tried checking if the server has access to the internet using the following netcat command:

nc -vz google.com 443

And it returned this output:

nc: connect to google.com port 443 (tcp) failed: Connection refused
nc: connect to google.com port 443 (tcp) failed: Network is unreachable

Instead of something like this:

Ncat: Version 7.70 ( https://nmap.org/ncat )
Ncat: Connected to 172.217.166.110:443.
Ncat: 0 bytes sent, 0 bytes received in 0.07 seconds.

I tried checking again if the server has access to the internet using the following wget command:

wget -q --spider http://google.com ; echo $?

And it returned:

Instead of:

Note: Anything other than 0 in the output means your system is not connected to the internet

I then tried the last time if the server has access to the internet using the following Nmap command:

nmap -p 443 google.com

And it returned:

Starting Nmap 7.01 ( https://nmap.org ) at 2021-02-16 11:50 WAT
Nmap scan report for google.com (216.58.223.238)
Host is up (0.00052s latency).
Other addresses for google.com (not scanned): 2c0f:fb50:4003:802::200e
rDNS record for 216.58.223.238: los02s04-in-f14.1e100.net
PORT    STATE  SERVICE
443/tcp closed https

Nmap done: 1 IP address (1 host up) scanned in 1.21 seconds

Instead something like this:

Starting Nmap 7.01 ( https://nmap.org ) at 2021-02-16 11:50 WAT
Nmap scan report for google.com (216.58.223.238)
Host is up (0.00052s latency).
Other addresses for google.com (not scanned): 2c0f:fb50:4003:802::200e
rDNS record for 216.58.223.238: los02s04-in-f14.1e100.net
PORT    STATE  SERVICE
443/tcp open https

Nmap done: 1 IP address (1 host up) scanned in 1.21 seconds

Note: The state of port 443/tcp is closed instead of open

All this was enough to make me realize that connections to the internet were not allowed on the server.

All I had to do was speak with the team in charge of infrastructure to fix the network connectivity issue to the internet on the server. And once that was fixed my docker command started working fine.

Resources: 9 commands to check if connected to internet with shell script examples

That's all.

I hope this helps

score 2 · Answer 13 · answered Mar 17 '22 at 14:26

2

On my windows 11 all I did was to first login into my account

docker login

answered Mar 17 '22 at 14:26

Shallon Kobusinge

447
5
9

score 1 · Answer 14 · answered Mar 10 '19 at 17:11

1

Got this from a network filter (LuLu on macOS) blocking traffic to/from Docker-related processes.

answered Mar 10 '19 at 17:11

jiku

283
5
16

In my case, Little Snitch was blocking a modified signature file. The main rules showed Docker as allowed, but Little Snitch had revoked access to a modified process. – Mukund Jun 24 '20 at 09:35

score 1 · Answer 15 · answered Mar 02 '20 at 09:33

1

I had this issue when I first installed Docker and ran

docker run hello-world

I was on a corporate network and switching to my personal network solved the issue for me.

answered Mar 02 '20 at 09:33

Amulya K Murthy

130
1
2
15

score 1 · Answer 16 · answered Mar 24 '20 at 09:38

The answers are provided here amazing, but if you are new in that and you don't realize full error then you may see at the end of that error net/http: TLS handshake timeout. message means that you have a slow internet connection. So it can be only that problem that's it. Toodles

Manu · Answer 17 · 2020-05-23T17:47:11.430

1

I had the following entries in my /etc/hosts file:

34.228.211.243  registry-1.docker.io
34.205.88.205   auth.docker.io
104.18.121.25   production.cloudflare.docker.com

Just by commenting them out, I fixed the problem.

edited May 23 '20 at 17:47

answered May 23 '20 at 16:20

Manu

11
2

HAltos · Answer 18 · 2021-03-10T19:22:35.903

List item

Many good answers above, but mine is a bit different with Mac and Docker Desktop UI. In my case, it is a Desktop proxy setting that needs to be turned off when I am outside of corporate fiewall/proxy:

ERROR message from docker CLI:
Username: xxx
Password: *** 
Error response from daemon: Get https://registry-1.docker.io/v2/: Service Unavailable

My env: Machine Mac with Docker UI (i.e. called Docker Desktop, shown as a whale icon), running outside of corp firewall/proxy.
I am able to Sign In with Docker Desktop UI.
However, whether docker login or docker pull, I kept getting the above error and I got sidetrack into the user id, reset the daemon, ...
Finally, I got to the Docker Desktop UI. Sure enough, there is a proxy setting that I have setup long time ago, and totally forgot about it!
Yes, when I am outside of firewall, I need to turn off the proxy setting here. Docker Desktop -> Preference -> Resources -> Proxies. Turn Turn off the manual proxy configuration. Then docker pull works (without docker login as I was pulling a public image)!

Thanks PS. I think the difference in behavior of Docker Desktop and Docker CLI contributes to the confusion. I am able to login to docker through the GUI, and the CLI keeps erroring out without good enough diagnostic information.

score 0 · Answer 19 · answered Mar 21 '22 at 17:32

0

Using Linux. For me it worked by doing:

$ docker logout
log out of hub.docker.com
log in to hub.docker.com
$ docker login

answered Mar 21 '22 at 17:32

jackjc9

11
1

score 0 · Answer 20 · edited Jul 19 '22 at 14:00

0

Check whether containers is enabled or not?

Goto --> turn on/off windows feature, then enable checkbox of containers
Restart windows.

edited Jul 19 '22 at 14:00

pzkpfw

565
3
21

answered Jul 14 '22 at 07:18

user19547343

1
1

score 0 · Answer 21 · edited Jul 26 '22 at 03:47

0

Using the root account instead of my regular user account solved it for me.

edited Jul 26 '22 at 03:47

tripleee

175,061
34
275
318

answered Jul 26 '22 at 03:32

dong xie

1

score -1 · Answer 22 · answered Apr 23 '20 at 05:50

-1

I have solved this issue about $ sudo docker run hello-world following the Docker doc.

If you are behind an HTTP Proxy server of corporate, this may solve your problem.

Docker doc also displays other situation about HTTP proxy setting.

answered Apr 23 '20 at 05:50

WangYang

466
1
5
15

score -1 · Answer 23 · answered Jun 01 '20 at 07:25

-1

In my case, stopping Proxifier fixed it. I added a rule to route any connections from vpnkit.exe as Direct and it now works.

answered Jun 01 '20 at 07:25

sashoalm

75,001
122
434
781

score -1 · Answer 24 · answered Jun 18 '20 at 06:40

-1

One of the problems you might need to check is, Does the registry requires VPN, Enable your VPN and try pulling again.

Thanks.

answered Jun 18 '20 at 06:40

user6223368 iSubodh

81
1
9

score -1 · Answer 25 · answered Jun 15 '21 at 23:02

Ok, I have a similar issue and nothing seemed to help, restart docker, disabled IPv6 and the nslookup and dig all seemed fine.

What worked for me was going to my Docker Desktop -> Preferences -> Experimental Features and unchecking Use new virtualization framework.

score -1 · Answer 26 · answered Jul 09 '21 at 12:06

-1

docker login terminal command worked for me.

If your machine requires VPN then must connect with VPN first and try docker login.

answered Jul 09 '21 at 12:06

Abhayam

327
1
3
6

The [same information](https://stackoverflow.com/a/62695719/2227743) has already [been posted](https://stackoverflow.com/a/62443828/2227743). – Eric Aya Jul 09 '21 at 12:28
Thanks, have the same issue when I stop VPN, it can download. – Luan Nguyen Sep 06 '21 at 12:59

score -1 · Answer 27 · answered Sep 30 '21 at 06:18

-1

Just reloading system, this is helped for me. (Windows 10 64x)

answered Sep 30 '21 at 06:18

trava

347
3
4

score -1 · Answer 28 · answered Apr 28 '22 at 19:39

-1

Have you create a repo with the matching tag on destinated docker hub? It might be that your container image has no where to be pushed to.

answered Apr 28 '22 at 19:39

that one guy on the internet

55
6

score -2 · Answer 29 · answered Aug 08 '19 at 13:18

-2

Run export DOCKER_CONTENT_TRUST=0 and then try it again.

answered Aug 08 '19 at 13:18

Michal Sipek

536
1
6
23

score -2 · Answer 30 · answered Jul 04 '21 at 16:41

-2

Use --tls in the pull request. For example if original pull request is docker pull dgraph/dgraph:v21.03.0 Use this instead : docker --tls pull dgraph/dgraph:v21.03.0

answered Jul 04 '21 at 16:41

Sidharth PJ

1

docker: Error response from daemon: Get https://registry-1.docker.io/v2/: Service Unavailable. IN DOCKER , MAC

30 Answers30

Linked