blocks|key|1498633|text|对我来说，当我第一次安装Docker并运行|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1498634|docker+run+hello-world|code-block|syntax|javascript|1498635|在运行以下命令时，我收到了一个要求身份验证的错误|1498636|curl+https://registry-1.docker.io/v2/+&&+echo+Works|1498637|我所需要做的就是重新启动我的MacOS，然后再次运行该命令，它刚刚开始拉取图像，然后我得到了消息|1498638|Hello+from+Docker!
This+message+shows+that+your+installation+appears+to+be+working+correctly.|1498639|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

For me I had this issue when I first installed Docker and ran
<pre><code>docker run hello-world
</code></pre>
I got an authentication required error when I ran
<pre><code>curl https://registry-1.docker.io/v2/ &amp;&amp; echo Works
</code></pre>
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
<pre><code>Hello from Docker!
This message shows that your installation appears to be working correctly.
</code></pre>

blocks|key|3871693|text|我试着在Windows上运行，在更新后遇到了这个问题。我尝试重新启动docker服务以及我的pc，但都不起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3871694|运行时：|3871695|curl+https://registry-1.docker.io/v2/+&&+echo+Works|code-block|syntax|javascript|3871696|我回来了：|3871697|{"errors":[{"code":"UNAUTHORIZED","message":"authentication+required","detail":null}]}
Works|3871698|最后，我尝试了：https://github.com/moby/moby/issues/22635#issuecomment-284956961|offset|length|3871699|将固定地址更改为8.8.8.8：|3871700|📷|atomic|3871701|​|3871702|这对我很有效！我仍然收到了curl+https://registry-1.docker.io/v2/的未经授权的消息，但我设法从docker+hub中提取了图像。|style|CODE|3871703|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/moby/moby/issues/22635#issuecomment-284956961|1|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/5a0a5fac3bd0a92b68d0bb757451ff0b.png|imageAlt^0|0|0|0|0|0|8|1S|0|0|0|0|1|1|0|0|D|11|0^^$0|@$1|2|3|4|5|6|7|1F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1G|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1H|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|1I|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|1J|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|1K|8|@]|9|@$O|1L|P|1M|1|1N]]|A|$]]|$1|Q|3|R|5|6|7|1O|8|@]|9|@]|A|$]]|$1|S|3|T|5|U|7|1P|8|@]|9|@$O|1Q|P|1R|1|1S]]|A|$]]|$1|V|3|W|5|6|7|1T|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1U|8|@$O|1V|P|1W|Z|10]]|9|@]|A|$]]|$1|11|3|-4|5|6|7|1X|8|@]|9|@]|A|$]]]|12|$13|$5|14|15|16|A|$17|18]]|19|$5|1A|15|1B|A|$1C|1D|1E|-4]]]]

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:

<pre><code>curl https://registry-1.docker.io/v2/ &amp;&amp; echo Works
</code></pre>

I got back: 

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

Eventually, I tried:
<a href="https://github.com/moby/moby/issues/22635#issuecomment-284956961" rel="noreferrer">https://github.com/moby/moby/issues/22635#issuecomment-284956961</a>

By changing the fixed address to 8.8.8.8:
<a href="https://i.stack.imgur.com/SOvoG.png" rel="noreferrer"><img src="https://i.stack.imgur.com/SOvoG.png" alt="enter image description here"></a>

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

blocks|key|1498672|text|尝试重新加载守护程序，然后重新启动docker服务。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1498673|systemctl+daemon-reload|code-block|syntax|javascript|1498674|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

try to reload daemon then restart docker service.
<pre><code>systemctl daemon-reload
</code></pre>

blocks|key|3871731|text|只是补充一下，以防其他人遇到这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3871732|在Mac上，我必须先注销再重新登录。|3871733|docker+logout

docker+login+|code-block|syntax|javascript|3871734|然后它会提示输入用户名(注意:不是电子邮件)和密码。(需要在https://hub.docker.com上开通账户才能下载图片)|offset|length|3871735|这对我来说很有效。|3871736|entityMap|0|LINK|mutability|MUTABLE|url|https://hub.docker.com/^0|0|0|0|U|M|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|Z|8|@]|9|@$K|10|L|11|1|12]]|A|$]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

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

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

<pre><code>docker logout

docker login 
</code></pre>

Then it prompts for username (NOTE: Not email) and password. (Need an account on <a href="https://hub.docker.com" rel="nofollow noreferrer">https://hub.docker.com</a> to pull images down)

Then it worked for me.

blocks|key|1498687|text|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|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1498688|这对我很有效|unstyled|1498689|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>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://&lt;&lt;IP OF CNTLM Proxy Server&gt;&gt;:3182”

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

Followed by:
systemctl daemon-reload

systemctl restart docker
</code></pre>

This Worked for me

blocks|key|1503345|text|这是从一个网络过滤器(macOS上的LuLu)拦截与Docker相关进程的流量得到的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1503346|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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

blocks|key|5288883|text|对我来说，这个问题是通过重新启动docker守护进程解决的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5288884|sudo+systemctl+restart+docker|code-block|syntax|javascript|5288885|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

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

<pre><code>sudo systemctl restart docker
</code></pre>

blocks|key|3871803|text|运行export+DOCKER_CONTENT_TRUST=0，然后重试。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3871804|entityMap^0|2|T|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Run <code>export DOCKER_CONTENT_TRUST=0</code> and then try it again.

blocks|key|1503383|text|其中一个选择在MAC上对我很有效。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1503384|单击托盘中的Docker图标。打开Preferences+->+Proxies。单击Manual+Proxy并以我们在HTTPS_PROXY环境变量中指定的相同格式指定Web+Server+(HTTP)代理和Secure+Web+server+(HTTPS)代理。选择应用并重新启动。|1503385|这对我很有效|1503386|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

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

blocks|key|3871884|text|这显然是一个代理问题:+https+docker将https连接代理到错误的位置。请记住，docker代理设置可能与操作系统(和curl)不同。下面是我是如何解决这个问题的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3871885|首先，找出你在哪里代理你的docker+https请求：|3871886|#+docker+info+%7C+grep+Proxy
Http+Proxy:+http://<my.proxy.server>:8080
Https+Proxy:+https://<my.proxy.server>:8080
No+Proxy:+localhost,127.0.0.1|code-block|syntax|javascript|3871887|仔细检查你的https设置。|3871888|在我的例子中，我意识到"Https+proxy“被设置为https://...而不是http://...，所以我在/etc/sysconfig/docker文件(我使用RHEL7)中更正了它，并在docker重新启动后使用：|offset|length|style|CODE|3871889|#+systemctl+restart+docker|3871890|代理变量显示已成功更新：|3871891|#+docker+info+%7C+grep+Proxy
Http+Proxy:+http://<my.proxy.server>:8080
Https+Proxy:+http://<my.proxy.server>:8080
No+Proxy:+localhost,127.0.0.1|3871892|一切运行正常:-)|3871893|entityMap^0|0|0|0|0|S|B|16|A|1L|L|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|12|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|13|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|14|8|@$M|15|N|16|O|P]|$M|17|N|18|O|P]|$M|19|N|1A|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|F|7|1B|8|@]|9|@]|A|$G|H]]|$1|S|3|T|5|6|7|1C|8|@]|9|@]|A|$]]|$1|U|3|V|5|F|7|1D|8|@]|9|@]|A|$G|H]]|$1|W|3|X|5|6|7|1E|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|Z|$]]

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:

<pre><code># docker info | grep Proxy
Http Proxy: http://&lt;my.proxy.server&gt;:8080
Https Proxy: https://&lt;my.proxy.server&gt;:8080
No Proxy: localhost,127.0.0.1
</code></pre>

and double check your https settings.

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

<pre><code># systemctl restart docker
</code></pre>

the proxy variable shows up succesfully updated:

<pre><code># docker info | grep Proxy
Http Proxy: http://&lt;my.proxy.server&gt;:8080
Https Proxy: http://&lt;my.proxy.server&gt;:8080
No Proxy: localhost,127.0.0.1
</code></pre>

and everything works fine :-)

blocks|key|5288994|text|我第一次安装Docker并运行时遇到了这个问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5288995|docker+run+hello-world|code-block|syntax|javascript|5288996|我在公司网络上，切换到我的个人网络为我解决了这个问题。|5288997|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I had this issue when I first installed Docker and ran

<pre><code>docker run hello-world
</code></pre>

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

blocks|key|3871924|text|这里提供了令人惊叹的答案，但如果你是新手，并且没有意识到完全错误，那么你可能会在错误消息的末尾看到net/http:+TLS+handshake+timeout.消息，这意味着你的互联网连接速度很慢。所以只能是那个问题了。图画|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3871925|entityMap^0|1D|W|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

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 <code>net/http: TLS handshake timeout.</code> message means that you have a slow internet connection. So it can be only that problem that's it. 
Toodles

blocks|key|1761500|text|我已经解决了$+sudo+docker+run+hello-world遵循Docker+doc的问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1761501|如果您使用的是公司的HTTP代理服务器，这可能会解决您的问题。|1761502|Docker+doc还可以显示有关HTTP+proxy设置的其他情况。|1761503|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.docker.com/config/daemon/systemd/|1^0|6|T|11|A|0|0|0|0|A|1|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@$9|V|A|W|1|X]]|E|$]]|$1|F|3|G|5|6|7|Y|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|Z|8|@]|D|@$9|10|A|11|1|12]]|E|$]]|$1|J|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]|R|$5|M|N|O|E|$P|Q]]]]

I have solved this issue about <code>$ sudo docker run hello-world</code> following the <a href="https://docs.docker.com/config/daemon/systemd/" rel="nofollow noreferrer">Docker doc</a>. 

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

<a href="https://docs.docker.com/config/daemon/systemd/" rel="nofollow noreferrer">Docker doc</a> also displays other situation about HTTP proxy setting.

blocks|key|5289055|text|我的/etc/hosts文件中有以下条目：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5289056|34.228.211.243++registry-1.docker.io
34.205.88.205+++auth.docker.io
104.18.121.25+++production.cloudflare.docker.com|code-block|syntax|javascript|5289057|只要把它们注释掉，我就解决了这个问题。|5289058|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

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

<pre><code>34.228.211.243 registry-1.docker.io
34.205.88.205 auth.docker.io
104.18.121.25 production.cloudflare.docker.com
</code></pre>

Just by commenting them out, I fixed the problem.

blocks|key|5289070|text|在我的例子中，停止Proxifier修复了它。我添加了一个规则，将来自vpnkit.exe的任何连接作为Direct路由，现在它可以工作了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|5289071|entityMap^0|Z|A|1G|6|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

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

blocks|key|3871992|text|您可能需要检查的问题之一是，注册表是否需要VPN，启用您的VPN并再次尝试拉取。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3871993|谢谢。|3871994|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

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

Thanks.

blocks|key|1761550|text|docker+logout
docker+login|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1761551|这可能会解决你的问题|unstyled|1761552|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>docker logout
docker login
</code></pre>
This might solve your problem

blocks|key|3872037|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3872038|使用以下命令重新检查代理设置|ordered-list-item|3872039|3872040|docker信息%7C+grep+Proxy|3872041|3872042|检查VPN连接|3872043|3872044|如果VPN不使用CHECK+NET+connectivity，则使用|3872045|3872046|3872047|3872048|重新安装Docker并重复上述步骤。|3872049|3872050|3872051|Enjoy|3872052|3872053|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|Y|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|Z|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|10|7|@]|8|@]|9|$]]|$1|E|3|F|4|5|6|11|7|@]|8|@]|9|$]]|$1|G|3|-4|4|5|6|12|7|@]|8|@]|9|$]]|$1|H|3|I|4|C|6|13|7|@]|8|@]|9|$]]|$1|J|3|-4|4|5|6|14|7|@]|8|@]|9|$]]|$1|K|3|L|4|5|6|15|7|@]|8|@]|9|$]]|$1|M|3|-4|4|C|6|16|7|@]|8|@]|9|$]]|$1|N|3|-4|4|5|6|17|7|@]|8|@]|9|$]]|$1|O|3|-4|4|5|6|18|7|@]|8|@]|9|$]]|$1|P|3|Q|4|C|6|19|7|@]|8|@]|9|$]]|$1|R|3|-4|4|5|6|1A|7|@]|8|@]|9|$]]|$1|S|3|-4|4|5|6|1B|7|@]|8|@]|9|$]]|$1|T|3|U|4|C|6|1C|7|@]|8|@]|9|$]]|$1|V|3|-4|4|5|6|1D|7|@]|8|@]|9|$]]|$1|W|3|-4|4|5|6|1E|7|@]|8|@]|9|$]]]|X|$]]

<ol>
<li>Recheck Proxy Settings with the following commands
docker info | grep Proxy
</li>
<li>Check VPN Connectivity
</li>
<li>If VPN not using CHECK NET connectivity
</li>
<li>Reinstall Docker and repeat the above steps.
</li>
<li>Enjoy
</li>
</ol>

blocks|key|1503498|text|在Ubuntu服务器上工作时，我也遇到了同样的问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1503499|我得到了以下错误：|1503500|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|code-block|syntax|javascript|1503501|下面是我尝试过的一些不起作用的东西|1503502|使用sudo+docker+systemctl+restart+docker|CODE|1503503|Powering+off重新启动docker服务，并在/etc/resolv.conf+|unordered-list-item|1503504|1503505|中重新启动Ubuntu+server.|1503506|
|1503507|Changing+|1503508|+to+8.8.8.8|1503509|1503510|1503511|这里是对我起作用的|1503512|我尝试使用以下netcat命令检查服务器是否可以访问互联网：|1503513|nc+-vz+google.com+443|1503514|并返回以下输出：|1503515|nc:+connect+to+google.com+port+443+(tcp)+failed:+Connection+refused
nc:+connect+to+google.com+port+443+(tcp)+failed:+Network+is+unreachable|1503516|而不是像这样：|1503517|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.|1503518|我尝试使用以下wget命令再次检查服务器是否可以访问互联网：|1503519|wget+-q+--spider+http://google.com+;+echo+$?|1503520|然后它返回了：|1503521|4|1503522|而不是：|1503523|0|1503524|注意：输出中除0以外的任何值都表示您的系统未连接到互联网|1503525|然后，我使用以下Nmap命令最后一次尝试服务器是否可以访问互联网：|1503526|nmap+-p+443+google.com|1503527|1503528|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|1503529|取而代之的是如下内容：|1503530|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|1503531|注意：端口443/tcp的状态是closed而不是open|1503532|所有这一切足以让我意识到，服务器上不允许连接到互联网。|1503533|我所要做的就是和负责基础设施的团队谈谈，解决服务器上互联网的网络连接问题。一旦解决了这个问题，我的docker命令就可以正常工作了。|1503534|资源：9+commands+to+check+if+connected+to+internet+with+shell+script+examples|1503535|就这样。|1503536|我希望这对有帮助|1503537|entityMap|LINK|mutability|MUTABLE|url|https://www.golinuxcloud.com/commands-check-if-connected-to-internet-shell/^0|1|6|0|0|0|0|H|0|2|10|0|R|G|0|0|0|0|0|0|0|0|0|9|0|7|6|0|0|0|0|0|0|7|4|0|0|0|0|0|0|0|2|0|8|4|0|0|0|0|0|0|0|2|G|6|P|4|5|7|0|0|0|0|2|3|1Z|0|0|0|0|5|0^^$0|@$1|2|3|4|5|6|7|2R|8|@$9|2S|A|2T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|2U|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|2V|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|2W|8|@$9|2X|A|2Y|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|2Z|8|@$9|30|A|31|B|Q]]|D|@]|E|$]]|$1|R|3|S|5|T|7|32|8|@$9|33|A|34|B|Q]]|D|@]|E|$]]|$1|U|3|-4|5|T|7|35|8|@]|D|@]|E|$]]|$1|V|3|W|5|6|7|36|8|@]|D|@]|E|$]]|$1|X|3|Y|5|6|7|37|8|@]|D|@]|E|$]]|$1|Z|3|10|5|T|7|38|8|@]|D|@]|E|$]]|$1|11|3|12|5|T|7|39|8|@]|D|@]|E|$]]|$1|13|3|-4|5|6|7|3A|8|@]|D|@]|E|$]]|$1|14|3|-4|5|6|7|3B|8|@]|D|@]|E|$]]|$1|15|3|16|5|6|7|3C|8|@$9|3D|A|3E|B|C]]|D|@]|E|$]]|$1|17|3|18|5|6|7|3F|8|@$9|3G|A|3H|B|Q]]|D|@]|E|$]]|$1|19|3|1A|5|J|7|3I|8|@]|D|@]|E|$K|L]]|$1|1B|3|1C|5|6|7|3J|8|@]|D|@]|E|$]]|$1|1D|3|1E|5|J|7|3K|8|@]|D|@]|E|$K|L]]|$1|1F|3|1G|5|6|7|3L|8|@]|D|@]|E|$]]|$1|1H|3|1I|5|J|7|3M|8|@]|D|@]|E|$K|L]]|$1|1J|3|1K|5|6|7|3N|8|@$9|3O|A|3P|B|Q]]|D|@]|E|$]]|$1|1L|3|1M|5|J|7|3Q|8|@]|D|@]|E|$K|L]]|$1|1N|3|1O|5|6|7|3R|8|@]|D|@]|E|$]]|$1|1P|3|1Q|5|J|7|3S|8|@]|D|@]|E|$K|L]]|$1|1R|3|1S|5|6|7|3T|8|@]|D|@]|E|$]]|$1|1T|3|1U|5|J|7|3U|8|@]|D|@]|E|$K|L]]|$1|1V|3|1W|5|6|7|3V|8|@$9|3W|A|3X|B|C]]|D|@]|E|$]]|$1|1X|3|1Y|5|6|7|3Y|8|@$9|3Z|A|40|B|Q]]|D|@]|E|$]]|$1|1Z|3|20|5|J|7|41|8|@]|D|@]|E|$K|L]]|$1|21|3|1O|5|6|7|42|8|@]|D|@]|E|$]]|$1|22|3|23|5|J|7|43|8|@]|D|@]|E|$K|L]]|$1|24|3|25|5|6|7|44|8|@]|D|@]|E|$]]|$1|26|3|27|5|J|7|45|8|@]|D|@]|E|$K|L]]|$1|28|3|29|5|6|7|46|8|@$9|47|A|48|B|C]|$9|49|A|4A|B|C]|$9|4B|A|4C|B|C]|$9|4D|A|4E|B|Q]]|D|@]|E|$]]|$1|2A|3|2B|5|6|7|4F|8|@]|D|@]|E|$]]|$1|2C|3|2D|5|6|7|4G|8|@]|D|@]|E|$]]|$1|2E|3|2F|5|6|7|4H|8|@$9|4I|A|4J|B|C]]|D|@$9|4K|A|4L|1|4M]]|E|$]]|$1|2G|3|2H|5|6|7|4N|8|@]|D|@]|E|$]]|$1|2I|3|2J|5|6|7|4O|8|@$9|4P|A|4Q|B|C]]|D|@]|E|$]]|$1|2K|3|-4|5|6|7|4R|8|@]|D|@]|E|$]]]|2L|$1U|$5|2M|2N|2O|E|$2P|2Q]]]]

I had this same issue when working on an Ubuntu server.
I was getting the following error:
<pre><code>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
</code></pre>
Here are the things I tried that did not work:
<ul>
<li>Restarting the docker service using <code>sudo docker systemctl restart docker</code></li>
<li>Powering off and restarting the Ubuntu server.</li>
<li>Changing the name server to 8.8.8.8 in the <code>/etc/resolv.conf</code> file</li>
</ul>
Here's what worked for me:
I tried checking if the server has access to the internet using the following <code>netcat</code> command:
<pre><code>nc -vz google.com 443
</code></pre>
And it returned this output:
<pre><code>nc: connect to google.com port 443 (tcp) failed: Connection refused
nc: connect to google.com port 443 (tcp) failed: Network is unreachable
</code></pre>
Instead of something like this:
<pre><code>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.
</code></pre>
I tried checking again if the server has access to the internet using the following <code>wget</code> command:
<pre><code>wget -q --spider http://google.com ; echo $?
</code></pre>
And it returned:
<pre><code>4
</code></pre>
Instead of:
<pre><code>0
</code></pre>
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 <code>Nmap</code> command:
<pre><code>nmap -p 443 google.com
</code></pre>
And it returned:
<pre><code>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
</code></pre>
Instead something like this:
<pre><code>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
</code></pre>
Note: The state of port <code>443/tcp</code> 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: <a href="https://www.golinuxcloud.com/commands-check-if-connected-to-internet-shell/" rel="nofollow noreferrer">9 commands to check if connected to internet with shell script examples</a>
That's all.
I hope this helps

blocks|key|1498881|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1498882|列表项|ordered-list-item|1498883|1498884|上面有很多不错的答案，但我的答案与Mac和Docker+Desktop+UI略有不同。在我的情况下，它是一个桌面代理设置，当我在公司fiewall/代理之外时，需要将其关闭：|1498885|ERROR+message+from+docker+CLI:
Username:+xxx
Password:+***+
Error+response+from+daemon:+Get+https://registry-1.docker.io/v2/:+Service+Unavailable|code-block|syntax|javascript|1498886|Docker+|1498887|My+env:运行在公司外部的带有Docker+UI的计算机firewall/proxy.|unordered-list-item|1498888|
|1498889|I能够登录Docker桌面UI。|1498890|1498891|1498892|1498893|无论是docker登录还是docker拉入，我一直收到上述错误，我转移到用户id，重置守护进程，...|1498894|1498895|最后，我到达了Docker+Desktop+UI。果然，有一个代理设置，我很久以前就设置了，但完全忘记了！|1498896|1498897|是的，当我在防火墙之外时，我需要在这里关闭代理设置。->桌面资源首选项Docker资源->代理。关闭手动代理配置。然后docker拉取工作(没有docker登录，因为我正在拉取公共镜像)！|1498898|1498899|谢谢，PS。我认为Docker+Desktop和Docker+CLI的行为差异导致了混乱。我可以通过GUI登录到docker，但CLI在没有足够好的诊断信息的情况下一直出错。|1498900|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|1A|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|1B|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|1C|7|@]|8|@]|9|$]]|$1|E|3|F|4|5|6|1D|7|@]|8|@]|9|$]]|$1|G|3|H|4|I|6|1E|7|@]|8|@]|9|$J|K]]|$1|L|3|M|4|5|6|1F|7|@]|8|@]|9|$]]|$1|N|3|O|4|P|6|1G|7|@]|8|@]|9|$]]|$1|Q|3|R|4|5|6|1H|7|@]|8|@]|9|$]]|$1|S|3|T|4|P|6|1I|7|@]|8|@]|9|$]]|$1|U|3|R|4|5|6|1J|7|@]|8|@]|9|$]]|$1|V|3|-4|4|P|6|1K|7|@]|8|@]|9|$]]|$1|W|3|R|4|5|6|1L|7|@]|8|@]|9|$]]|$1|X|3|Y|4|P|6|1M|7|@]|8|@]|9|$]]|$1|Z|3|R|4|5|6|1N|7|@]|8|@]|9|$]]|$1|10|3|11|4|P|6|1O|7|@]|8|@]|9|$]]|$1|12|3|R|4|5|6|1P|7|@]|8|@]|9|$]]|$1|13|3|14|4|P|6|1Q|7|@]|8|@]|9|$]]|$1|15|3|-4|4|5|6|1R|7|@]|8|@]|9|$]]|$1|16|3|17|4|5|6|1S|7|@]|8|@]|9|$]]|$1|18|3|-4|4|5|6|1T|7|@]|8|@]|9|$]]]|19|$]]

<ol>
<li>List item</li>
</ol>
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:
<pre><code>ERROR message from docker CLI:
Username: xxx
Password: *** 
Error response from daemon: Get https://registry-1.docker.io/v2/: Service Unavailable
</code></pre>
<ol>
<li>My env: Machine Mac with Docker UI (i.e. called Docker Desktop,
shown as a whale icon), running outside of corp firewall/proxy.</li>
<li>I am able to Sign In with Docker Desktop UI.</li>
<li>However, whether docker login or docker pull, I kept getting the above error and I got sidetrack into the user id, reset the daemon, ...</li>
<li>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!</li>
<li>Yes, when I am outside of firewall, I need to turn off the proxy setting here.
Docker Desktop -&gt; Preference -&gt; Resources -&gt; Proxies. Turn
Turn off the manual proxy configuration.
Then docker pull works (without docker login as I was pulling a public image)!</li>
</ol>
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.

blocks|key|5289271|text|好吧，我有一个类似的问题，似乎没有任何帮助，重启docker，禁用IPv6和nslookup和dig看起来都很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5289272|对我起作用的是进入我的Docker+Desktop+->偏好设置->实验功能，并取消选中使用新的虚拟化框架。|5289273|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

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 -&gt; Preferences -&gt; Experimental Features and unchecking Use new virtualization framework.

blocks|key|5289285|text|在拉取请求中使用--tls。例如，如果原始拉取请求为docker+pull+dgraph/dgraph:v21.03.0，则改为使用以下内容：docker+--tls+pull+dgraph/dgraph:v21.03.0|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|5289286|entityMap^0|8|5|Q|Y|1Z|14|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

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

blocks|key|1498941|text|docker登录终端命令对我有效。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1498942|如果您的计算机需要VPN，则必须先连接到VPN，然后尝试docker登录。|1498943|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

docker login terminal command worked for me.
If your machine requires VPN then must connect with VPN first and try docker login.

blocks|key|3872212|text|只是重新加载系统，这对我很有帮助。(Windows+10+64x)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3872213|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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

I am having this issue in my Mac system 10.11.6
<pre><code>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
</code></pre>
<hr />
<pre><code>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'.
</code></pre>
I have looked for a solution that says to set proxy, but I have set the proxy for the wifi.
<a href="https://docs.docker.com/docker-for-mac/networking/#httphttps-proxy-support" rel="noreferrer">https://docs.docker.com/docker-for-mac/networking/#httphttps-proxy-support</a>
Still, it is not working.
I have set proxy for docker too. It is not working.
in Preference -&gt; 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?

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

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我在我的Mac系统10.11.6中遇到这个问题system3:postgres saurabh-gupta2$ docker build -t postgres .Sending build context to Docker daemon  38.91kBStep 1/51 : FROM registry.acces...

问docker:来自守护进程的错误响应:获取https://registry-1.docker.io/v2/:服务不可用。在DOCKER中，MAC
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问docker:来自守护进程的错误响应:获取https://registry-1.docker.io/v2/:服务不可用。在DOCKER中，MACEN