Access to images through index.docker.io fails with 404

[konrad-o]

Problem description

Accessing docker image through https://index.docker.io/ gives 404 error. Images can be searched through that URL, but when you want to navigate to specific image it shows 404.

Example: index.docker.io OK: https://index.docker.io/search?q=git-branches&source=community 404: https://index.docker.io/r/aoldershaw/git-branches-resource

hub.docker.com OK: https://hub.docker.com/search?q=git-branches&source=community OK: https://hub.docker.com/r/aoldershaw/git-branches-resource

I applies to many images. Seems like a problem with /r/ in the url. Official images with /_/ in url work fine https://index.docker.io/_/debian https://index.docker.io/_/ubuntu

But with /r/ don't https://index.docker.io/r/docker/github-actions https://index.docker.io/r/bitnami/tomcat

Debug Information

Browser name and version: Any browser

URL: https://index.docker.io

Timestamp or time range: We discovered it started somewhere between 19th and 22nd of November.

Public IP:

Hub Username:

Error messages (on screen or in browser console)

Our CI started to fail on retrieval of that particular image.

ERRO[0000] download failed: get image: GET https://index.docker.io/v2/aoldershaw/git-branches-resource/manifests/: unexpected status code 404 Not Found: 404 page not found 

Screenshots of the issue (if applicable)

Task List

• [x] This is NOT a security issue
• [x] I do NOT have a Docker subscription
• [x] I have looked through other issues and they do NOT apply to me

[ingshtrom]

@konrad-o Thank you for the report. I think I see two issues in this report, so I'm going to try and separate them so I can understand everything.

Firstly, index.docker.io is not the correct domain to use to access the Docker Hub Web UI. Instead, you should always use hub.docker.com. I know this is confusing and we are working on correcting that confusion. Please, use hub.docker.com.

The CI start failing on 11/19-11/22, right? What command was run that failed? Is your CI scraping our APIs or was a docker pull done?

[konrad-o]

Thank for the quick reply. We're using Concourse CI and this error appears during common step that downloads the image (so I guess docker pull). It is therefore used to run CI task inside container based on that image. We're not using anything custom and url (host) that is reached to get the image is defined internally in the Concourse. I assumed that something must have changed on dockerhub side in that date range, because we haven't changed anything in that pipeline definition for few months, we haven't updated our CI & suddenly it started to fail. Do you have any clue why? Why index.docker.io was working fine and now it stopped? I can have a look into concourse code to check how image is retrieved.

[ingshtrom]

Do you have any clue why? Why index.docker.io was working fine and now it stopped?

It is odd that it started failing suddenly. I can confirm that docker pull aoldershaw/git-branches-resource and docker pull index.docker.io/aoldershaw/git-branches-resource work locally, so there is nothing wrong with pulling images.

I will check with some internal teams about changes during that time frame.