Closed PavloZabudskyi closed 2 years ago
registry.hub.docker.com is returning 301 which redirects to hub.docker.com which then returns 404 and HTML responses.
This is being investigated. It is recommended that you use registry-1.docker.io
to pull/push images from/to Docker Hub and hub.docker.com
to reach the UI/non-registry-api parts of Docker Hub, but I don't think we provided an official deprecation notice.
We will fix it for now, but I suggest switching to the domains I mentioned above.
I will let you know once it is fixed.
switching to registry-1.docker.io
is still giving us 404s when pulling images from our private registry.
edit: private image, not private registry.
According to docker info
, the default registry used by the docker client is index.docker.io
What are the differences with registry-1.docker.io
?
Can confirm that both registry-1.docker.io
and docker.io
are working for private registries for push/pull from/to Docker Hub in Kubernetes with an updated docker-registry
secret that points to the new server for imagePullSecrets
Everything looks to be working properly. We did a full rollback as of 13:40 UTC today, so we are at the same state we were at about 24 hours ago.
@mkrakowitzer When you say private registry, do you mean a private image on Docker Hub? If you are truly pulling from a private registry, then you will want to use the URL of that registry, but none of the stuff in this issue should be affecting you, unless you are using it as a pull-through cache for Docker Hub.
@adam-lebon they all point to the same backend services, so really it is only a difference in the hostname which has occurred over many years of changes (much of which predates me). I will inquire further with the corresponding teams as to which hostname is correct and if it isn't index.docker.io
, why the engine defaults to that.
@Callumccr thank you, it is good news to see if validated from others as well.
Thank you all, please report if there are any other issues and please include any errors or specific commands you are using to reproduce it.
Should we look at switching to registry-1.docker.io
as a temporary workaround or is that the long-term solution?
Should we look at switching to
registry-1.docker.io
as a temporary workaround or is that the long-term solution?
+1 on this, will there be a deprecation notice in the future?
We are making an API call like HEAD /v2/<name>/manifests/<reference>
. What is the best-practice FQDN for that API call?
The recommended hostname to be used to hit the Docker Hub registry is registry-1.docker.io
and the recommended hostname to hit Docker Hub UI is hub.docker.com
. I said legacy in some posts around the Internet, but I realize these were based off of passed down knowledge throughout the years at Docker without being documented. Thus all hostnames are still valid, but we will be looking to officially document the correct hostnames to be using for all of our products soon. Any deprecation (I'm not saying it's happening, but if it happens) will be communicated through our official channels well in advance likely along with brownout periods.
Sorry for the confusion and inconvenience.
@andscho-msft that would be registry-1.docker.io
as that is a request directly to the Docker Hub registry.
Problem description
We can't pull/push to
registry.hub.docker.com
anymore. Was it deprecated? There are onlyregistry-1.docker.io
andregistry.docker.io
at https://status.docker.com/ mentioned