Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error - blob unknown to registry. Is it OK ? #21638

Open
pierrevillard opened this issue Feb 14, 2025 · 4 comments
Open

Error - blob unknown to registry. Is it OK ? #21638

pierrevillard opened this issue Feb 14, 2025 · 4 comments
Assignees

Comments

@pierrevillard
Copy link

Hello,

In need help on "blob unknown to registry". And i didn't find anything that can help me on internet to solve this...

Context:

  • I use Harbor 2.12.2, in HA model on an AWS EKS cluster v1.32 with Redis (Helm bitnami) and AWS RDS Postgres.
  • Cache for metadata, projects,... is enabled on Redis.
  • Storage is filesystem on AWS EFS.
  • All Harbor services are replicated with 4 replicas.
  • Harbor ingess use "nginx-ingress"
  • All harbor services are UP and works as espected.

Sometimes, when i push images on registry, i notice this kind of error => "blob unknown to registry"
This error don't break push, that success everytime, but I don't understand why i got this... Does it's a true error ? What can i do to correct it ?

time="2025-02-14T08:52:17.446353828Z" level=error msg="response completed with error" auth.user.name="harbor_registry_user" err.code="blob unknown" err.detail=sha256:1f3e46996e2977e4faa5846e56e76e3748b7315e2ded61476c24403d592134f0 err.message="blob unknown to registry" go.version=go1.23.4 http.request.host=repository.hp.cloud-factory.dma.dsit.aws.internal.cloud.edf.fr http.request.id=2cb63744-85ac-4650-8efd-88b9220bdd7a http.request.method=HEAD http.request.remoteaddr=10.0.0.98 http.request.uri="/v2/test/nginx/blobs/sha256:1f3e46996e2966e4faa5846e56e76e3748b7315e2ded61476c24403d592134f0" http.request.useragent="skopeo/1.4.1" http.response.contenttype="application/json; charset=utf-8" http.response.duration=107.803496ms http.response.status=404 http.response.written=157 vars.digest="sha256:1f3e46996e2977e4faa5846e56e76e3748b7315e2ded61476c24403d592134f0" vars.name="test/nginx"

Have you any idea ?

Thank !

@wy65701436
Copy link
Contributor

Hi, if you're using the Bitnami Harbor Helm chart, please file an issue on their repository first. If it's confirmed as a core team issue, feel free to bring it back to us. Thanks!

@pierrevillard
Copy link
Author

Hi,

I use Goharbor helm chart : https://goharbor.io/docs/1.10/install-config/harbor-ha-helm/.
The onlu Bitnami helm chart i use is for Redis HA cluster with sentinel.

@wy65701436
Copy link
Contributor

it seems that your redis has some dirty data which will cause the 404 problem during image pushing. Can you please clean the redis firstly(the database of registry, and the default should be 2)? Then try to push again.

@pierrevillard
Copy link
Author

hi @wy65701436

Thanks for your help !
I flushed Redis master data and this error 404 "blob unknown to registry" is still here. Is it a true error ? Maybe it's normal, i d'ont know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants