Can't pull any containers for the registries `unknown blob`

I’m currently not able to pull any image for any registry on
I’m getting the following:

docker image pull
Using default tag: latest
latest: Pulling from companyname/app
26c5c85e47da: Already exists 
9e79879be9c7: Already exists 
5dd57ff8d411: Already exists 
50349b1ecdeb: Already exists 
431f8d1d6c10: Already exists 
4f4fb700ef54: Pulling fs layer 
7cffeea1f9d7: Pulling fs layer 
ebc7bb5199cf: Pulling fs layer 
c6c85ed2806a: Waiting 
b8217bc618be: Waiting 
error pulling image configuration: download failed after attempts=1: unknown blob

Anyone else has this issue or knows how to fix it?


yes same issue for me.
I think gitlab accidentally deleted all container images.
see this registry

1 Like

Same issue. Also when checking images in the registry it constantly updates the create datetime.

1 Like

Experiencing this issue as well. Every refresh of an container image page also shows it as published “just now”.

Yeah same here, a colleague of mine has the start of the unix epoch though (firefox).

as a temp workaround, some gitlab images can be found on Docker
we can download them and push to our private container registries

In our case it’s images in our private registries that are affected.

I see. that means the whole is affected. I am using self managed gitlab thankfully so my private images are working :sweat_smile:

1 Like

Also seeing this issue when pulling an image for CI:

ERROR: Job failed: failed to pull image "" with specified policies [always]: error pulling image configuration: unknown blob (manager.go:237:0s)

We’re also seeing this in our CI pipelines that try to use private images:
ERROR: failed to solve: failed to copy: httpReadSeeker: failed open: could not fetch content descriptor sha256:xxxxxxxxxxxx (application/vnd.docker.container.image.v1+json) from remote: not found

they finally acknowledged the issue on gitlab status page thankfully

1 Like

Now showing ‘active incident’.


Incident is still open, but I am able to pull images at the moment.

Same issue. I am still unable to pull images.
Images used in production…

able to pull my images now. i think they are recovering

Thanks for reporting. This incident is tracked and updated in 2023-05-12: Container registry pulls failing with unknown blob (#14260) · Issues · / GitLab Infrastructure Team / production · GitLab


Pushing doesn’t work either:

Thanks everyone for reporting this. We’re deploying a fix for the problem on container registry pulls failing.

Details in 2023-05-12: Container registry pulls failing with unknown blob (#14260) · Issues · / GitLab Infrastructure Team / production · GitLab

1 Like