Hi,
I have a docker file, that worked yesterday, but now I’m running into a problem. The problem seems to be with the connectivity of registry-1.docker.io:
=> ERROR [internal] load metadata for docker.io/library/gcc:12.1.0-bullseye 30.0s
------
> [internal] load metadata for docker.io/library/gcc:12.1.0-bullseye:
------
DockerfileLinux:1
--------------------
1 | >>> FROM gcc:12.1.0-bullseye
2 |
3 | RUN git clone --depth 1 --branch v3.23.3 https://gitlab.kitware.com/cmake/cmake.git && \
--------------------
ERROR: failed to solve: DeadlineExceeded: DeadlineExceeded: DeadlineExceeded: gcc:12.1.0-bullseye: failed to do request: Head "https://registry-1.docker.io/v2/library/gcc/manifests/12.1.0-bullseye": dial tcp 44.205.64.79:443: i/o timeout
Is there something I can do about this, or I just have to wait till the service is up again?
I’m sorry to hear that you’re facing issues with your Dockerfile. The error message you’re seeing suggests that there’s a connectivity issue with the Docker registry at the moment. It’s possible that the registry is currently down or experiencing high traffic, which could cause a timeout.
Before taking any further steps, I’d recommend checking the status of the Docker registry to see if there are any known issues or scheduled maintenance. You can do this by visiting the Docker status page at https://status.docker.com/.
If there are no known issues, you can try the following troubleshooting steps:
Check your internet connection to ensure that you’re not experiencing any connectivity issues.
Try running the docker build command with the --no-cache option to ensure that you’re not using any cached images that may be causing issues.
Try using a different Docker registry mirror to see if that resolves the issue. You can set a different registry mirror by adding the --registry-mirror flag followed by the URL of the mirror you want to use.
If none of these steps work, then it’s possible that the issue is with the Docker registry itself, and you may need to wait for it to come back online. In the meantime, you could try building your Docker image using a different base image or a different version of the same base image.
Hi Eden,
thank you for the response. Two days later, the problem was gone. I don’t think that registry-1.docker.io was unavailable to all users over that time. I guess, I would have read about it somewhere, if larger parts of the world would have been unable to build docker containers. On the other hand, I did not recognized any other internet connection issues. The build process of one of my software products rely on docker and I feel pretty bad about the chance, that parts of the build fail to work due to issues like this for so long.
Where could I see a list of mirrors, that I could use, if that issue happens again?
I have the same issue with my server connection. It’s weird somethins it works. I think it’s related to my IAS provider OVH. I have timeout when I tried to download a docker image or even with a telnent.
docker pull jenkins/ssh-agent
Using default tag: latest
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 happened to me as well after I upgraded my Docker desktop to the latest version. So I just restarted it after trying some other solutions (like connecting my my VPN and disconnecting from it). If somebody had same problem I would suggest to restart your docker process (in case you are on linux) or restart your docker desktop