Images are not available while still no vulnerability analysis are available

I’ve got a feeling that the recent official library/docker images are not available while the vulnerability scans are not done yet. Still didn’t find any official policy or guide about this behavior, though they may exist.

When trying to pull docker:dind for example, my docker client reports that “manifest for docker:latest not found: manifest unknown: manifest unknown”. This is that case for other images as well, where the hub.docker.com page says that the analysis is still not available. It’s quite unfortunate that the latest tags are overwritten before the test are being performed.

Is my feeling right? Are the latest tags globally unavailable?

It seems to not be working for me either, perhaps use an older version?

Using the latest tag is not recommended, but I agree it shouldn’t be a reason to publish a tag and still block pulling it. If you want, you can report it on GitHub

I can’t confirm the behavior, because I don’t think I ever experienced it, but it could be.

Yeah, the latest non-RC tag for my specific image is 27.3-dind, however the topic is rather about the phenomenon, not the specific image.

Well, this tag is not the “latest”, but the latest of its kind, though (almost?) non of the tags currently published on https://hub.docker.com/_/docker are available at the moment.

So, if you want to experience something new, just type docker pull docker:27.4.0 in your terminal. :slight_smile:

Ticket has been opened: Pulling published tags (eg.: latest) is denied until vulnerability scans are finished · Issue #2426 · docker/hub-feedback · GitHub

1 Like

Ok, I could reproduce it with your suggested command. So it is worse than I thought. I hope it can be improved. Thanks for creating the ticket.

Yup, all manifests uploaded 10 hours ago

Accourding to the Docker status notification, they indentified the root cause and are working on it. In case the status changes later, this is the current one:

[Identified] Some images in the following repositories can fail to be pulled with a not found: manifest unknown error

api-firewall arangodb bash crate docker drupal friendica ghost haproxy irssi julia matomo openjdk rabbitmq redmine ruby

We have identified the root cause an are working on remediation the issue

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.