Docker Community Forums

Share and learn in the Docker community.

Windows 10 Home - Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

Docker Hub
#1

I am extremely frustrated with Docker Hub at the moment and have done everything to try to login to Docker from my Windows Home PC. This worked 100% a few weeks ago, but all of a sudden get the error the following error message:
Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

Here is my problem and actions I tried:

  1. I use Windows 10 Home, with WSL2 Enabled and Docker for Windows installed.
  2. I am NOT behind a proxy, so the internet is open from my home PC
  3. I can build and run Docker containers locally
  4. I can view Remote Repositories on Docker for Windows
  5. I disabled my Windows Defender and local windows firewall, but get the same issue.
  6. I created a new Docker account with no repositories, but get the same issue
  7. I updated the password to make sure its not the wrong password

As explained in the top sentence, this worked 100% for me only a few weeks ago.

Anyone, please help if you had the same problem and have a fix for me.

Thanks

#2

Could you solve this? I experience the same problems since yesterday. I’m running Linux, no Proxy, no VPN. Cannot ping docker.io. Switching DNS in /etc/resolv.conf did not solve the problem either.

#3

(create a copy of config.json if you have special configuration)
docker logout
#delete config.json file
docker login --username your-DockerID-not-your-email
password: **that’s it**

It should create the config.json again.
I know it sound stupid but believe me I know your pain.
Just in case you’re getting that message while trying to login from a script take a look at this issue I opened a couple of hours ago

#4

Thanks for your suggestion but it didn’t work out for me:

[me@home .docker]$ docker logout
[me@home .docker]$ docker login --username fpmaon
Password: 
Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

It seems to me that a network issue is most likely. But I cannot find out what’s wrong …

#5

Try connecting using a different device, if possible with a general public dns like 8.8.8.8
This should tell you if the problem is from your computer, your dns, or the server

#6

Changed the DNS before but it didn’t help. Also switching to another network (to a friend of mine) did not solve the problem …

#7

I delete the config file as suggested, but it didn’t made a difference.

My config is stored under my C:\User\xxxx.docker\

This is what it created, even though I added my Docker ID.

{
“auths”: {},
“credsStore”: “wincred”
}

#8

@thesolutionarchitect @fpmaon I’m sorry I forgot how docker runs on windows, try this:
Start Docker Desktop that’s the problem
try login when it’s ready (just in case try logout first)
Good luck

#9

In my case it’s embarrassing: I pinned the IP of docker.io in my /etc/hosts and it seems like it changed … :man_facepalming:
Removing the entry fixed my problem …

#10

Oh yes i am also geting this error please follow this link click here

#11

Most of the time the problem is a silly mistake. When complexity begins to grow, it is natural that these problems drive us crazy. Especially when you jump from one project to another.
I’m glad to see you solved your problem

#12

My Docker Desktop works fine and I can even login within the Desktop app to Docker Hub. However, I cannot login using Powershell or in Visual Studio Code’s terminal, which also uses Powershell.

#13

I just solved it by entering the Access Token in the Docker Desktop app. Then all commands via powershell worked.

#14

Thanks so much. The access token worked. All I had to do is logout of the Docker for Windows App, enter my Docker ID and the access token as the password and it worked.