This also worked for me!
For anyone that is not on a corporate VPN, uses a proxy, or has made any changes from the installation. I previously re-installed my OS to find my fresh installation of Docker also facing this 503 Error Response.
For my solution, I simply restarted my router (power off/on) and re-connected to the network. The response error resolved itself. Hope this helps anyone!
to those who still in headache about this issue:
It bother me for whole afternoon. Tried all different ways can find from google search.
- remove hosts configuration items.
- restart servciesā¦
after #service stop docker checked service status seems āokā, but dockerd and containerd still runningā¦
manually killed and restart service again - no luck. - ā¦
finally, Iām thinking it may be some system errors are hard to manipulate manually.
reboot linux system , issue gone.
just want to provide an alternative āsolutionāā¦
good luck everyone.
Hello Chat!
Actually, yours computers havenāt any kind of viruses and firwall problems.
2022 + win764 pro + docker toolbox + this TRUE ELEGANT SOLUTION = success!!!
Tnx lot Dear vladkras! ;0)
None of the above works for me. Running on a VM with Windows server 2022 and WSL2.
Latest version of docker and ubuntu. I have tried:
-All sorts of restarts and reinstalls
-Setting manually DNS to 8.8.8.8 and 8.8.4.4
-Messing with proxy settings (even though I am NOT behind proxy)
-Dropped the firewall
-Running Powershell as admin
When I use windows containers I usually get this error:
Error response from daemon: Get āhttps://registry-1.docker.io/v2/ā: read tcp 172.16.44.129:8609->44.205.64.79:443: wsarecv: An existing connection was forcibly closed by the remote host.
And when I switch to linux containers I get:
Error response from daemon: Get āhttps://registry-1.docker.io/v2/ā: net/http: TLS handshake timeout
Trying to login with docker login results the same error.
Everything else works fine on the machine and the internet connection is very fast.
I have docker on debug mode but the logs are not very helpful.
Any ideas on how to debug this are more than welcome.
Thank you.
Iām sorry for necroposting, but I guess Iāve found the solution, and thereās no other place to post how Iāve solved it.
Iāve had two interfaces in my VM, and one of them was bridged to my network interface via VMWare Workstation functional, the other was subnetwork NATed to the same direction. Itās not the loop problem, because disabling the NATed one didnāt solve the problem.
It looks like the docker was using the bridged one (due to metrics or smth).
The problem was solved by disabling the bridged interface, but you can probably fix it by changing metrics, routes or something else.
If thats not the case for you, some people suggest that it may be the firewall, DLP or proxy fail.