Docker run hello-world - Get "https://registry-1.docker.io/v2/": Service Unavailable

lfthiang · March 23, 2022, 4:16am

When I was using Docker Desktop 4.5.1, my docker was running fine. Suddenly, one week later, I hit the following error message when I tried to do a docker build which pulls python:3-slim image.

=> ERROR [internal] load metadata for docker.io/library/python:3-slim                                             0.0s
------
 > [internal] load metadata for docker.io/library/python:3-slim:
------
failed to solve with frontend dockerfile.v0: failed to create LLB definition: failed to do request: Head "https://registry-1.docker.io/v2/library/python/manifests/3-slim": dial tcp 174.129.220.74:443: connect: connection refused

I have updated to the latest Docker Desktop 4.6.1 (76265). I am running Windows 10 Education 21H2.

C:\>docker run hello-world
Unable to find image 'hello-world:latest' locally
docker: Error response from daemon: Get "https://registry-1.docker.io/v2/": Service Unavailable.
See 'docker run --help'.

I have tried the following:

Use Docker Desktop to clean / purge data + docker system prune
Use Docker Desktop to reset to factory default
Change DNS to 8.8.8.8
Uninstall, reboot and install again.

When i run the diagnostic tool
C:\>"C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check
There is this failed test.

[FAIL] DD0012: is the VM networking working? network checks failed: failed to ping host: exit status 1
[2022-03-23T04:00:30.557559800Z][com.docker.diagnose.exe][I] ipc.NewClient: 3f8b03a6-diagnose-network -> \\.\pipe\dockerDiagnosticd diagnosticsd
[common/pkg/diagkit/gather/diagnose.runIsVMNetworkingOK()
[       common/pkg/diagkit/gather/diagnose/network.go:34 +0xdd
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x18a63a0)
[       common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x18a63a0)
[       common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2, 0x18a63a0)
[       common/pkg/diagkit/gather/diagnose/run.go:140 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x18a63a0, 0xc000661830)
[       common/pkg/diagkit/gather/diagnose/run.go:146 +0x36
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x1000000013bb7a0, 0xc000661830)
[       common/pkg/diagkit/gather/diagnose/run.go:149 +0x73
[common/pkg/diagkit/gather/diagnose.walkOnce(0x1223ec0, 0xc00035f970)
[       common/pkg/diagkit/gather/diagnose/run.go:135 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x18a6420, 0xc00035fb48, {0xc00035fb00, 0x1, 0x1})
[       common/pkg/diagkit/gather/diagnose/run.go:16 +0x1ce
[main.checkCmd({0xc0000643d0, 0xc0000643d0, 0x4}, {0x0, 0x0})
[       common/cmd/com.docker.diagnose/main.go:131 +0x105
[main.main()
[       common/cmd/com.docker.diagnose/main.go:97 +0x273
[2022-03-23T04:00:30.558087400Z][com.docker.diagnose.exe][I] (6dc411c7) 3f8b03a6-diagnose-network C->S diagnosticsd POST /check-network-connectivity: {"ips":["10.20.3.247","172.23.176.1","172.18.144.1","192.168.199.1","192.168.52.1","192.168.10.115"]}
[2022-03-23T04:00:31.132314000Z][com.docker.diagnose.exe][E] (6dc411c7) 3f8b03a6-diagnose-network C<-S e0b53e92-diagnosticsd POST /check-network-connectivity (574.7542ms): failed to ping host: exit status 1
[common/pkg/diagkit/gather/diagnose.runIsVMNetworkingOK()
[       common/pkg/diagkit/gather/diagnose/network.go:35 +0x15b
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x18a63a0)
[       common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x18a63a0)
[       common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2, 0x18a63a0)
[       common/pkg/diagkit/gather/diagnose/run.go:140 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x18a63a0, 0xc000661830)
[       common/pkg/diagkit/gather/diagnose/run.go:146 +0x36
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x1000000013bb7a0, 0xc000661830)
[       common/pkg/diagkit/gather/diagnose/run.go:149 +0x73
[common/pkg/diagkit/gather/diagnose.walkOnce(0x1223ec0, 0xc00035f970)
[       common/pkg/diagkit/gather/diagnose/run.go:135 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x18a6420, 0xc00035fb48, {0xc00035fb00, 0x1, 0x1})
[       common/pkg/diagkit/gather/diagnose/run.go:16 +0x1ce
[main.checkCmd({0xc0000643d0, 0xc0000643d0, 0x4}, {0x0, 0x0})
[       common/cmd/com.docker.diagnose/main.go:131 +0x105
[main.main()
[       common/cmd/com.docker.diagnose/main.go:97 +0x273

I am not behind any proxy server. My colleague, on the same network, does not encounter any issue, and we are both using our company laptops; i.e. should be similar configuration.

My config.json
{"credsStore":"desktop","debug":true}

My daemon.json

{
    "builder": { "gc": { "defaultKeepStorage": "20GB", "enabled": true } },
    "experimental": false,
    "features": { "buildkit": true },
    "debug":true
}

I will appreciate any advice how to solve or troubleshoot further. Thanks in advance!

lfthiang · March 24, 2022, 1:09am

I execute docker run hello-world in command prompt and post the added lines in dockerd.log and log.txt below.

C:\Users\lfthiang\AppData\Local\Docker\log\vm\dockerd.log

[2022-03-24T00:50:38.336864500Z][dockerd][I] time="2022-03-24T00:50:38.336724500Z" level=debug msg="Calling HEAD /_ping"
[2022-03-24T00:50:38.555511200Z][dockerd][I] time="2022-03-24T00:50:38.555380700Z" level=debug msg="Calling HEAD /_ping"
[2022-03-24T00:50:38.884708500Z][dockerd][I] time="2022-03-24T00:50:38.884532800Z" level=debug msg="Calling HEAD /_ping"
[2022-03-24T00:50:40.018507300Z][dockerd][I] time="2022-03-24T00:50:40.017853700Z" level=debug msg="Calling POST /v1.41/containers/create"
[2022-03-24T00:50:40.019918100Z][dockerd][I] time="2022-03-24T00:50:40.019251000Z" level=debug msg="form data: {\"AttachStderr\":true,\"AttachStdin\":false,\"AttachStdout\":true,\"Cmd\":null,\"Domainname\":\"\",\"Entrypoint\":null,\"Env\":null,\"HostConfig\":{\"AutoRemove\":false,\"Binds\":null,\"BlkioDeviceReadBps\":null,\"BlkioDeviceReadIOps\":null,\"BlkioDeviceWriteBps\":null,\"BlkioDeviceWriteIOps\":null,\"BlkioWeight\":0,\"BlkioWeightDevice\":[],\"CapAdd\":null,\"CapDrop\":null,\"Cgroup\":\"\",\"CgroupParent\":\"\",\"CgroupnsMode\":\"\",\"ConsoleSize\":[30,120],\"ContainerIDFile\":\"\",\"CpuCount\":0,\"CpuPercent\":0,\"CpuPeriod\":0,\"CpuQuota\":0,\"CpuRealtimePeriod\":0,\"CpuRealtimeRuntime\":0,\"CpuShares\":0,\"CpusetCpus\":\"\",\"CpusetMems\":\"\",\"DeviceCgroupRules\":null,\"DeviceRequests\":null,\"Devices\":[],\"Dns\":[],\"DnsOptions\":[],\"DnsSearch\":[],\"ExtraHosts\":null,\"GroupAdd\":null,\"IOMaximumBandwidth\":0,\"IOMaximumIOps\":0,\"IpcMode\":\"\",\"Isolation\":\"\",\"KernelMemory\":0,\"KernelMemoryTCP\":0,\"Links\":null,\"LogConfig\":{\
[2022-03-24T00:50:40.029806300Z][dockerd][I] time="2022-03-24T00:50:40.029520200Z" level=debug msg="Calling GET /v1.41/info"
[2022-03-24T00:50:42.673067700Z][dockerd][I] time="2022-03-24T00:50:42.672753300Z" level=debug msg="Calling POST /v1.41/images/create?fromImage=hello-world&tag=latest"
[2022-03-24T00:50:42.677528400Z][dockerd][I] time="2022-03-24T00:50:42.677283000Z" level=debug msg="Trying to pull hello-world from https://registry-1.docker.io v2"
[2022-03-24T00:50:42.698408400Z][dockerd][I] time="2022-03-24T00:50:42.698283200Z" level=warning msg="Error getting v2 registry: Get \"https://registry-1.docker.io/v2/\": Service Unavailable"
[2022-03-24T00:50:42.698454500Z][dockerd][I] time="2022-03-24T00:50:42.698321900Z" level=info msg="Attempting next endpoint for pull after error: Get \"https://registry-1.docker.io/v2/\": Service Unavailable"
[2022-03-24T00:50:42.700694600Z][dockerd][I] time="2022-03-24T00:50:42.700602100Z" level=error msg="Handler for POST /v1.41/images/create returned error: Get \"https://registry-1.docker.io/v2/\": Service Unavailable"

C:\Users\lfthiang\AppData\Local\Docker\log.txt

[2022-03-24T00:50:38.335336000Z][com.docker.proxy.exe][I] proxy >> HEAD /_ping
[2022-03-24T00:50:38.336971400Z][com.docker.proxy.exe][I] proxy << HEAD /_ping (1.7194ms)
[2022-03-24T00:50:38.553995400Z][com.docker.proxy.exe][I] proxy >> HEAD /_ping
[2022-03-24T00:50:38.555650800Z][com.docker.proxy.exe][I] proxy << HEAD /_ping (1.6554ms)
[2022-03-24T00:50:38.883178900Z][com.docker.proxy.exe][I] proxy >> HEAD /_ping
[2022-03-24T00:50:38.884752000Z][com.docker.proxy.exe][I] proxy << HEAD /_ping (1.5731ms)
[2022-03-24T00:50:38.899139500Z][com.docker.proxy.exe][I] (e98b9138) de1fa007-ProxyCMD C->S CSharpAPI POST /usage: {"command":"containerCreateCliLinux","count":1}
[2022-03-24T00:50:40.007126900Z][IPCServer         ][Info   ] (e98b9138) bc22ca38-CSharpAPI S<-C de1fa007-ProxyCMD POST /usage
github.com/docker/pinata/common/pkg/gui.(*guiClient).Usage(0xc0002a64e0, 0x174a85e)
	C:/workspaces/PR-17529/src/github.com/docker/pinata/common/pkg/gui/client.go:129 +0x44
github.com/docker/pinata/common/pkg/proxy.(*GuiAnalytics).sendCommand(0xc000112b80, {0x174a85e, 0xf}, {0x1740090, 0x3}, 0x1)
	C:/workspaces/PR-17529/src/github.com/docker/pinata/common/pkg/proxy/analytics.go:104 +0xe9
github.com/docker/pinata/common/pkg/proxy.(*GuiAnalytics).trackRouteForHTTPMethod(0x1856080, 0xc000454300, 0x160dc20, 0x1782700)
	C:/workspaces/PR-17529/src/github.com/docker/pinata/common/pkg/proxy/analytics.go:97 +0xf4
github.com/docker/pinata/common/pkg/proxy.(*GuiAnalytics).Middleware.func1({0x1850cd0, 0xc00047c1c0}, 0xc000454300)
	C:/workspaces/PR-17529/src/github.com/docker/pinata/common/pkg/proxy/analytics.go:59 +0x8d
github.com/gorilla/mux.(*Router).ServeHTTP(0xc0003940c0, {0x1850cd0, 0xc00047c1c0}, 0xc000454100)
	C:/workspaces/PR-17529/src/github.com/docker/pinata/vendor/github.com/gorilla/mux/mux.go:210 +0x1cf
[2022-03-24T00:50:40.009301200Z][IPCServer         ][Info   ] (e98b9138) bc22ca38-CSharpAPI S->C de1fa007-ProxyCMD POST /usage (1ms): OK
[2022-03-24T00:50:40.012849700Z][com.docker.proxy.exe][I] (e98b9138) de1fa007-ProxyCMD C<-S bc22ca38-CSharpAPI POST /usage (1.1137102s): OK
[2022-03-24T00:50:40.013377300Z][com.docker.proxy.exe][I] usage containerCreateCliLinux + 1
[2022-03-24T00:50:40.013525100Z][com.docker.proxy.exe][I] proxy >> POST /v1.41/containers/create
[2022-03-24T00:50:40.025296300Z][com.docker.proxy.exe][I] proxy << POST /v1.41/containers/create (11.7712ms)
[2022-03-24T00:50:40.027178700Z][com.docker.proxy.exe][I] proxy >> GET /v1.41/info
[2022-03-24T00:50:40.042466700Z][com.docker.proxy.exe][I] proxy << GET /v1.41/info (15.288ms)
[2022-03-24T00:50:42.605365400Z][com.docker.proxy.exe][I] (11d94266) de1fa007-ProxyCMD C->S CSharpAPI POST /usage: {"command":"imagePullCliLinux","count":1}
[2022-03-24T00:50:42.665620600Z][IPCServer         ][Info   ] (11d94266) bc22ca38-CSharpAPI S<-C de1fa007-ProxyCMD POST /usage
github.com/docker/pinata/common/pkg/gui.(*guiClient).Usage(0xc00000cae0, 0x1745af0)
	C:/workspaces/PR-17529/src/github.com/docker/pinata/common/pkg/gui/client.go:129 +0x44
github.com/docker/pinata/common/pkg/proxy.(*GuiAnalytics).sendCommand(0xc000112b80, {0x1745af0, 0x9}, {0x1740090, 0x3}, 0x1)
	C:/workspaces/PR-17529/src/github.com/docker/pinata/common/pkg/proxy/analytics.go:104 +0xe9
github.com/docker/pinata/common/pkg/proxy.(*GuiAnalytics).trackRouteForHTTPMethod(0x1856080, 0xc000510500, 0x160dc20, 0x1782700)
	C:/workspaces/PR-17529/src/github.com/docker/pinata/common/pkg/proxy/analytics.go:97 +0xf4
github.com/docker/pinata/common/pkg/proxy.(*GuiAnalytics).Middleware.func1({0x1850cd0, 0xc0005e61c0}, 0xc000510500)
	C:/workspaces/PR-17529/src/github.com/docker/pinata/common/pkg/proxy/analytics.go:59 +0x8d
github.com/gorilla/mux.(*Router).ServeHTTP(0xc0003940c0, {0x1850cd0, 0xc0005e61c0}, 0xc000510300)
	C:/workspaces/PR-17529/src/github.com/docker/pinata/vendor/github.com/gorilla/mux/mux.go:210 +0x1cf
[2022-03-24T00:50:42.666434300Z][IPCServer         ][Info   ] (11d94266) bc22ca38-CSharpAPI S->C de1fa007-ProxyCMD POST /usage (0ms): OK
[2022-03-24T00:50:42.668518300Z][com.docker.proxy.exe][I] (11d94266) de1fa007-ProxyCMD C<-S bc22ca38-CSharpAPI POST /usage (63.1529ms): OK
[2022-03-24T00:50:42.668518300Z][com.docker.proxy.exe][I] usage imagePullCliLinux + 1
[2022-03-24T00:50:42.668518300Z][com.docker.proxy.exe][I] proxy >> POST /v1.41/images/create?fromImage=hello-world&tag=latest
[2022-03-24T00:50:42.668518300Z][com.docker.proxy.exe][I] (7a639904) e7f3db32-ProxyPKG C->S BackendAPI GET /registry/access
[2022-03-24T00:50:42.669749300Z][com.docker.backend.exe][I] (7a639904) caad92f8-BackendAPI S<-C e7f3db32-ProxyPKG GET /registry/access
[2022-03-24T00:50:42.670262700Z][GoBackendProcess  ][Info   ] [common/pkg/backend.(*backendClient).GetAccess(0xc0001003c0)
[2022-03-24T00:50:42.670426700Z][GoBackendProcess  ][Info   ] [	common/pkg/backend/client.go:258 +0x62
[2022-03-24T00:50:42.670522500Z][GoBackendProcess  ][Info   ] [common/pkg/proxy.(*ramPullApprover).Approve(0x23e753c1a98, {{0x17459be, 0x9}, {0x0, 0x0}, {0x1743be6, 0x7}, {0xc0001201b4, 0xb}, {0xc0001201c4, ...}})
[2022-03-24T00:50:42.670572500Z][GoBackendProcess  ][Info   ] [	common/pkg/proxy/pull.go:34 +0x25
[2022-03-24T00:50:42.670602700Z][GoBackendProcess  ][Info   ] [common/pkg/proxy.(*proxyPullRewriter).RequestRewrite(0xc0003541d0, 0xc000510500)
[2022-03-24T00:50:42.670602700Z][GoBackendProcess  ][Info   ] [	common/pkg/proxy/pull.go:61 +0xf5
[2022-03-24T00:50:42.670602700Z][GoBackendProcess  ][Info   ] [common/pkg/proxy.(*passthrough).doHandleHTTP(0xc0001011d0, {0x23e7548c298, 0xc0006824a0}, {0x1850cd0, 0xc0005e61c0}, 0x2, {0xc00026f510, 0x14d62e6, 0x1db9a80})
[2022-03-24T00:50:42.670602700Z][GoBackendProcess  ][Info   ] [	common/pkg/proxy/passthrough.go:181 +0xfc
[2022-03-24T00:50:42.670602700Z][GoBackendProcess  ][Info   ] [common/pkg/proxy.(*passthrough).HandleHTTP(0xc0001011d0, {0x1850cd0, 0xc0005e61c0}, 0xc000510500)
[2022-03-24T00:50:42.670602700Z][GoBackendProcess  ][Info   ] [	common/pkg/proxy/passthrough.go:116 +0x41e
[2022-03-24T00:50:42.670602700Z][GoBackendProcess  ][Info   ] [common/pkg/proxy.withError.func1({0x1850cd0, 0xc0005e61c0}, 0xc00026f590)
[2022-03-24T00:50:42.670602700Z][GoBackendProcess  ][Info   ] [	common/pkg/proxy/routes.go:16 +0x3c
[2022-03-24T00:50:42.670602700Z][GoBackendProcess  ][Info   ] [common/pkg/proxy.NewRouter.func2.1({0x1850cd0, 0xc0005e61c0}, 0xc000510500)
[2022-03-24T00:50:42.670602700Z][GoBackendProcess  ][Info   ] [	common/pkg/proxy/proxy.go:107 +0x2f4
[2022-03-24T00:50:42.670602700Z][GoBackendProcess  ][Info   ] [common/pkg/proxy.NewRouter.func1.1({0x1850cd0, 0xc0005e61c0}, 0xc000510500)
[2022-03-24T00:50:42.670602700Z][GoBackendProcess  ][Info   ] [	common/pkg/proxy/proxy.go:76 +0x142
[2022-03-24T00:50:42.670602700Z][GoBackendProcess  ][Info   ] [common/pkg/proxy.(*restrictions).Middleware.func1({0x1850cd0, 0xc0005e61c0}, 0xc000510500)
[2022-03-24T00:50:42.671112400Z][GoBackendProcess  ][Info   ] [	common/pkg/proxy/restrictions.go:75 +0x154
[2022-03-24T00:50:42.671159900Z][GoBackendProcess  ][Info   ] [common/pkg/proxy.(*GuiAnalytics).Middleware.func1({0x1850cd0, 0xc0005e61c0}, 0xc000510500)
[2022-03-24T00:50:42.671159900Z][GoBackendProcess  ][Info   ] [	common/pkg/proxy/analytics.go:61 +0xac
[2022-03-24T00:50:42.671159900Z][GoBackendProcess  ][Info   ] [github.com/gorilla/mux.(*Router).ServeHTTP(0xc0003940c0, {0x1850cd0, 0xc0005e61c0}, 0xc000510300)
[2022-03-24T00:50:42.671159900Z][GoBackendProcess  ][Info   ] [	vendor/github.com/gorilla/mux/mux.go:210 +0x1cf
[2022-03-24T00:50:42.670602700Z][com.docker.backend.exe][I] (7a639904) caad92f8-BackendAPI S->C e7f3db32-ProxyPKG GET /registry/access (1.2681ms): {"allowed":[{"DNS":"","IP":{"IP":"0.0.0.0","Mask":"AAAAAA=="},"Type":1,"value":"0.0.0.0/0"},{"DNS":".","IP":{"IP":"","Mask":null},"Type":3,"value":"."}],"enabled":false,"refresh_after":"2022-03-24T20:50:42.6702627+08:00","refresh_grace_period_ends":"2022-03-25T08:50:42.6702627+08:00","refresh_grace_period_interval":3600000000000}
[2022-03-24T00:50:42.671159900Z][com.docker.proxy.exe][I] (7a639904) e7f3db32-ProxyPKG C<-S caad92f8-BackendAPI GET /registry/access (2.6416ms): {"allowed":[{"DNS":"","IP":{"IP":"0.0.0.0","Mask":"AAAAAA=="},"Type":1,"value":"0.0.0.0/0"},{"DNS":".","IP":{"IP":"","Mask":null},"Type":3,"value":"."}],"enabled":false,"refresh_after":"2022-03-24T20:50:42.6702627+08:00","refresh_grace_period_ends":"2022-03-25T08:50:42.6702627+08:00","refresh_grace_period_interval":2884905626637435000}
time="2022-03-24T00:50:42.683246374Z" level=info msg="ethernet: Connected Ethernet interface f6:16:36:bc:f9:c6"
time="2022-03-24T00:50:42.683246374Z" level=info msg="udp: UDP interface connected on 192.168.65.1"
time="2022-03-24T00:50:42.696243047Z" level=info msg="http: HTTP proxy --> 52.202.132.224:443 Host:registry-1.docker.io:443 (Origin): CONNECT "
time="2022-03-24T00:50:42.696243047Z" level=error msg="http: HTTP proxy --> 52.202.132.224:443 Host:registry-1.docker.io:443 (Origin): Failed to connect to 52.202.132.224:443"
time="2022-03-24T00:50:42.696243047Z" level=info msg="http: HTTP proxy: returning 503 Service_unavailable"
[2022-03-24T00:50:42.700892600Z][com.docker.proxy.exe][I] proxy << POST /v1.41/images/create?fromImage=hello-world&tag=latest (32.3743ms)
[2022-03-24T00:50:42.713013000Z][com.docker.backend.exe][I] (a5440789) 48957ae2-CLIAPI S<-C Go-http-client/1.1 POST /usage
[2022-03-24T00:50:42.713013000Z][com.docker.backend.exe][I] (a5440789) 48957ae2-CLIAPI S<-C Go-http-client/1.1 bind: {"command":"run","context":"moby","source":"cli","status":"failure"}
[2022-03-24T00:50:42.713013000Z][com.docker.backend.exe][I] (a5440789-1) 24450b8e-BackendCMD C->S CSharpAPI POST /usage/cli: {"command":"run","context":"moby","source":"cli","status":"failure"}
[2022-03-24T00:50:42.736442600Z][IPCServer         ][Info   ] (a5440789-1) bc22ca38-CSharpAPI S<-C 24450b8e-BackendCMD POST /usage/cli
github.com/docker/pinata/common/pkg/gui.(*guiClient).CliUsage(0xc0006a2540, 0x2504a20)
	C:/workspaces/PR-17529/src/github.com/docker/pinata/common/pkg/gui/client.go:147 +0x44
github.com/docker/pinata/common/cmd/com.docker.backend/internal/server.appendCliRoutes.func2({0x2504a20, 0xc0006a2540})
	C:/workspaces/PR-17529/src/github.com/docker/pinata/common/cmd/com.docker.backend/internal/server/routes.go:170 +0xb4
[2022-03-24T00:50:42.738726100Z][IPCServer         ][Info   ] (a5440789-1) bc22ca38-CSharpAPI S->C 24450b8e-BackendCMD POST /usage/cli (2ms): OK
[2022-03-24T00:50:42.739295200Z][com.docker.backend.exe][I] (a5440789-1) 24450b8e-BackendCMD C<-S bc22ca38-CSharpAPI POST /usage/cli (26.2822ms): OK
[2022-03-24T00:50:42.739295200Z][com.docker.backend.exe][I] (a5440789) 48957ae2-CLIAPI S->C Go-http-client/1.1 POST /usage (26.2822ms): OK

Also note that if I switch to Windows containers, I am able to execute docker run hello-world in command prompt successfully without errors. The error occurs when I am using Linux containers,

It is very puzzling to me. I appreciate any help or advice. Thanks in advance.

stanislavpresnecov · March 25, 2022, 5:41pm

I faced the same issue. Docker was working fine, but maybe after windows update (KB5011487, KB4023057) I can’t run docker in any way, neither docker pull nor docker run and so on. As a result, I always get “Error response from daemon: Get “https://registry-1.docker.io/v2/”: Service Unavailable” (depending on the installed version).
I tried to change versions of docker, tried to rollback windows updates (totally useless).
I updated wsl, but it also had no effect…

smatcaboji · March 28, 2022, 8:37am

Faced the same issue, it was working fine one day and then all of a sudden without any software or hardware updates, docker did not want to pull any images.
Tried to unintall and reinstall docker , wsl but with no results. Also created a ticket on the docker support but i did not get any answers.
I managed to get it working by reinstalling windows.

ssilenzi · March 31, 2022, 2:44pm

Same issue as @stanislavpresnecov and @smatcaboji. I tried to reinstall Docker, change version, update WSL, but nothing seems to solve the issue. The support didn’t answer the question.

lfthiang · March 31, 2022, 11:47pm

I did more troubleshooting.

I load a linux image to Docker Desktop using TAR and I can run a container.
I login into the container to do apt-get update. I get the following error

# apt-get update
Err:1 http://deb.debian.org/debian bullseye InRelease
  Could not connect to debian.map.fastlydns.net:80 (199.232.46.132). - connect (111: Connection refused) Unable to connect to deb.debian.org:http:
Err:2 http://deb.debian.org/debian bullseye-updates InRelease
  Unable to connect to deb.debian.org:http:
Err:3 http://security.debian.org/debian-security bullseye-security InRelease
  Could not connect to debian.map.fastlydns.net:80 (199.232.46.132). - connect (111: Connection refused) Could not connect to security.debian.org:80 (151.101.194.132). - connect (111: Connection refused) Could not connect to security.debian.org:80 (151.101.2.132). - connect (111: Connection refused) Could not connect to security.debian.org:80 (151.101.66.132). - connect (111: Connection refused) Could not connect to security.debian.org:80 (151.101.130.132). - connect (111: Connection refused)
Reading package lists... Done
W: Failed to fetch http://deb.debian.org/debian/dists/bullseye/InRelease  Could not connect to debian.map.fastlydns.net:80 (199.232.46.132). - connect (111: Connection refused) Unable to connect to deb.debian.org:http:
W: Failed to fetch http://security.debian.org/debian-security/dists/bullseye-security/InRelease  Could not connect to debian.map.fastlydns.net:80 (199.232.46.132). - connect (111: Connection refused) Could not connect to security.debian.org:80 (151.101.194.132). - connect (111: Connection refused) Could not connect to security.debian.org:80 (151.101.2.132). - connect (111: Connection refused) Could not connect to security.debian.org:80 (151.101.66.132). - connect (111: Connection refused) Could not connect to security.debian.org:80 (151.101.130.132). - connect (111: Connection refused)
W: Failed to fetch http://deb.debian.org/debian/dists/bullseye-updates/InRelease  Unable to connect to deb.debian.org:http:
W: Some index files failed to download. They have been ignored, or old ones used instead.

Secondly, @ stanislavpresnecov mentioned windows update (KB5011487, KB4023057) . I didn’t have those updates when I first had this issue.

Hope these help to provide more information for troubleshooting.

rimelek · April 2, 2022, 1:51am

Every time I see someone has network issue on WSL2 I have to mention that WSL2 gets its IP address from the same IP range as Docker does. It doesn’t always cause any problem, but since WSL2 doesn’t know about Docker, Windows can choose the same subnet as one of the docker networks or an overlapping subnet.

I know, it is about Docker Desktop and Docker desktop has a static IP address, so it can’t be the same problem, but it can be something similar if the host network somehow changed. You can try to change the IP address of Docker Desktop in Settings or you can try to find out what is the problem.

Normally I would try run a container on the host network and mount the root filesystem of the Docker Desktop VM:

docker run --rm -it --net host nicolaka/netshoot bash

and then I would check the network. For example:

ip addr
tracepath 8.8.8.8

If you can download that image from an other host too and load the exported tar archive, you can still try it. I don’t remember the other way exactly, but I had to run nsenter from the WSL distribution after I found out which process is in the right namespace.

ssilenzi · April 8, 2022, 10:55am

I did the same steps as you and I get the same errors

onlineeric · April 12, 2022, 2:39am

same issue here.
I previously posted my question on Stackoverflow.
The issue still not resolved.

ssilenzi · April 14, 2022, 7:46am

I solved the problem by upgrading to early version 4.8.0

https://desktop-stage.docker.com/win/main/amd64/77236/Docker%20Desktop%20Installer.exe

What has generated the issue is still unknown

lfthiang · April 22, 2022, 1:21am

Thanks for sharing. Unfortunately, I still have the same error with 4.8.0.

richerna2 · May 6, 2022, 6:47pm

Hello, is there any update to this? I have the same error as well. New to Docker

lfthiang · May 9, 2022, 12:14am

No. I still have the issue on my Windows.

I have been running a Linux VM with docker to workaround this. The VM is on the same machine.

haibeiz · May 12, 2022, 11:55am

My 2year old docker was working fine. Then I hit the “upgrade” button and it lost internet for every command. My error message is slightly different.

Error response from daemon: Get “https://registry-1.docker.io/v2/”: unable to connect to 54.85.245.135:443. Do you need an HTTP proxy?

I’ve tried many reinstall/restart, set experimental and buildkit to “false”, switching between hyperv and wsl2. Nothing worked.

gguyantmednet · May 18, 2022, 7:39pm

I and my team have been experiencing the same thing. Anyone figure out a successful resolution. We’ve tried pretty much the same attempted fixes to no avail. We also tried reinstalling a lower version with no success.

For each our of 4 devs, this started occurring when we upgraded.

I’ve had some success by using a Linux install in WSL and using docker from there (similar to Ifthiang). That said, its a pretty inconvenient workaround so I’m interested in the root problem here.

jscottrcu · May 31, 2022, 7:34pm

Just want to throw my hat in the ring and say my team is experiencing this as well. We had Docker desktop working fine on Windows for a few months, then we all we started experiencing this issue after a Windows update. We are currently working with our IT staff to see if this may be an anti-virus issue, but currently no luck.

borgesalexandre · May 31, 2022, 8:17pm

Hi. I’m getting the same error when pulling a Linux docker image in a Windows 10 Pro machine:

(HTTP code 500) server error - Get “https://registry-1.docker.io/v2/”: unable to connect to 52.200.78.26:443. Do you need an HTTP proxy?

If I switch to Windows containers, the network problem = disappear, but the image I’m trying to pull is = Linux, so the error changes to:

image operating system “linux” cannot be used on this platform.

docker run hello-world => works fine when I choose Windows container.

lfthiang · June 20, 2022, 12:06am

I had posted in Docker Desktop for Windows Github forum too but, sadly, no action to date.

github.com/docker/for-win

docker pull ... Error response from daemon: Get "https://registry-1.docker.io/v2/": ...

opened 01:49AM - 26 May 22 UTC

lfthiang

## Diagnostics ID - [X] I have tried with the latest version of Docker Des…ktop - [X] I have tried disabling enabled experimental features - [X] I have uploaded Diagnostics - Diagnostics ID: 26624E28-712F-4563-B4F6-7768405E55A1/20220526011441 ### Actual behavior Unable to docker pull images (or access network). ### Expected behavior Should be able to docker pull images. ### Information - Is it reproducible? Yes - Is the problem new? No. I first had the issue in Mar with Docker Desktop for Windows 4.5.1 See https://forums.docker.com/t/docker-run-hello-world-get-https-registry-1-docker-io-v2-service-unavailable/122531 I am still having issue with the current version 4.8.2 (79419) - Did the problem appear with an update? No. I was using Docker Desktop 4.5.1 with no issue. It just appears one day. Please refer to my post on Docker forum https://forums.docker.com/t/docker-run-hello-world-get-https-registry-1-docker-io-v2-service-unavailable/122531 From what I know, there was no Windows update & I did not change any software either. - A reproducible case if this is a bug, Dockerfiles with reproduction inside is best. Please see steps to reproduce the behaviour below. - Windows Version: Windows 10 Education version 21H2 OS build 19044.1586 - Docker Desktop Version: 4.8.2 (79419) - WSL2 or Hyper-V backend? WSL2 - Are you running inside a virtualized Windows e.g. on a cloud server or a VM: No. Running native on my laptop ### Output of `& "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check` Starting diagnostics [PASS] DD0027: is there available disk space on the host? [PASS] DD0028: is there available VM disk space? [PASS] DD0031: does the Docker API work? [PASS] DD0004: is the Docker engine running? [PASS] DD0011: are the LinuxKit services running? [PASS] DD0016: is the LinuxKit VM running? [PASS] DD0001: is the application running? [SKIP] DD0018: does the host support virtualization? [PASS] DD0002: does the bootloader have virtualization enabled? [PASS] DD0017: can a VM be started? [PASS] DD0024: is WSL installed? [PASS] DD0021: is the WSL 2 Windows Feature enabled? [PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled? [PASS] DD0025: are WSL distros installed? [PASS] DD0026: is the WSL LxssManager service running? [PASS] DD0029: is the WSL 2 Linux filesystem corrupt? [PASS] DD0015: are the binary symlinks installed? [PASS] DD0003: is the Docker CLI working? [PASS] DD0013: is the $PATH ok? [FAIL] DD0005: is the user in the docker-users group? The specified domain either does not exist or could not be contacted. [PASS] DD0007: is the backend responding? [PASS] DD0014: are the backend processes running? [PASS] DD0008: is the native API responding? [PASS] DD0009: is the vpnkit API responding? [PASS] DD0010: is the Docker API proxy responding? [PASS] DD0006: is the Docker Desktop Service responding? [FAIL] DD0012: is the VM networking working? network checks failed: failed to ping host: exit status 1 [2022-05-26T01:41:54.285207400Z][com.docker.diagnose.exe][I] ipc.NewClient: b0531f5d-diagnose-network -> \\.\pipe\dockerDiagnosticd diagnosticsd [common/pkg/diagkit/gather/diagnose.runIsVMNetworkingOK() [ common/pkg/diagkit/gather/diagnose/network.go:34 +0xdd [common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x1251960) [ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43 [common/pkg/diagkit/gather/diagnose.Run.func1(0x1251960) [ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a [common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2?, 0x1251960) [ common/pkg/diagkit/gather/diagnose/run.go:140 +0x77 [common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x1251960, 0xc000079730) [ common/pkg/diagkit/gather/diagnose/run.go:146 +0x36 [common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0xcb00000012?, 0xc000079730) [ common/pkg/diagkit/gather/diagnose/run.go:149 +0x73 [common/pkg/diagkit/gather/diagnose.walkOnce(0xc1a960?, 0xc00025f890) [ common/pkg/diagkit/gather/diagnose/run.go:135 +0xcc [common/pkg/diagkit/gather/diagnose.Run(0x1251f60, 0xc14300?, {0xc00025fb20, 0x1, 0x1}) [ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1cb [main.checkCmd({0xc0000a63b0?, 0xc0000a63b0?, 0x4?}, {0x0, 0x0}) [ common/cmd/com.docker.diagnose/main.go:132 +0x105 [main.main() [ common/cmd/com.docker.diagnose/main.go:98 +0x27f [2022-05-26T01:41:54.285207400Z][com.docker.diagnose.exe][I] (795d3539) b0531f5d-diagnose-network C->S diagnosticsd POST /check-network-connectivity: {"ips":["172.17.64.1","192.168.16.1","192.168.199.1","192.168.52.1","192.168.10.115"]} [2022-05-26T01:41:54.838944900Z][com.docker.diagnose.exe][W] (795d3539) b0531f5d-diagnose-network C<-S 46c4b8e0-diagnosticsd POST /check-network-connectivity (553.7375ms): failed to ping host: exit status 1 [FAIL] DD0032: do Docker networks overlap with host IPs? network bridge has subnet 172.17.0.0/16 which overlaps with host IP 172.17.64.1 [SKIP] DD0030: is the image access management authorized? [PASS] DD0033: does the host have Internet access? Please investigate the following 3 issues: 1 : The test: is the user in the docker-users group? Failed with: The specified domain either does not exist or could not be contacted. The current user must be member of the docker-users group. Press the Win + R keys to open Run, type lusrmgr.msc into Run, followed by Enter to open Local Users and Groups. 2 : The test: is the VM networking working? Failed with: network checks failed: failed to ping host: exit status 1 VM seems to have a network connectivity issue. Please check your host firewall and anti-virus settings in case they are blocking the VM. 3 : The test: do Docker networks overlap with host IPs? Failed with: network bridge has subnet 172.17.0.0/16 which overlaps with host IP 172.17.64.1 If the subnet used by a Docker network overlaps with an IP used by the host, then containers won't be able to contact the overlapping IP addresses. Please try configuring the IP address range used by networks: in your docker-compose.yml. See https://docs.docker.com/compose/compose-file/compose-file-v2/#ipv4_address-ipv6_address #### Notes on the diagnostic results - Failed with: The specified domain either does not exist or could not be contacted. I am not on my corporate network when I ran the diagnostic tool. - Failed with: network bridge has subnet 172.17.0.0/16 which overlaps with host IP 172.17.64.1 I had tried changing the subnet range by adding the following lines to daemon.json via Settings > Docker Engine. This diagnostic is gone but I still have the "docker pull" problem. ``` "default-address-pools": [ {"base":"10.10.0.0/16","size":24} ] ``` ### Steps to reproduce the behavior ``` C:\>docker pull python:3-slim Error response from daemon: Get "https://registry-1.docker.io/v2/": unable to connect to 52.72.255.218:443. Do you need an HTTP proxy? C:\>docker run hello-world Unable to find image 'hello-world:latest' locally docker: Error response from daemon: Get "https://registry-1.docker.io/v2/": unable to connect to 54.144.118.70:443. Do you need an HTTP proxy?. See 'docker run --help'. ```

gkoraysaritas · June 28, 2022, 5:34am

I get exactly the same problem on Windows 10 version 21H2 and Docker version 4.9.1. I have been dealing with this issue for almost two months. Does anyone know how to fix this?

brown131 · June 29, 2022, 12:43pm

Due to the unresponsiveness of Docker regarding this issue, our Windows users have had to switch over to Rancher Desktop, which has a docker CLI. https://rancherdesktop.io/

Topic		Replies	Views
Unable to run the hello-world Docker Desktop windows	4	5568	September 28, 2017
Issue with registry-1.docker.io Docker Desktop	0	1265	December 30, 2019
Registry access Docker Desktop windows	2	2702	June 19, 2018
Error response from daemon: Get "Https://registry-1.docker.io/v2/": Docker Desktop	0	745	May 4, 2023
Docker run hello-world results in an error General docker	2	6727	August 5, 2022

Docker run hello-world - Get "https://registry-1.docker.io/v2/": Service Unavailable

Related topics