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 response from daemon: unknown: artifact, after upgraded harbor to v2.6.2 #17852

Closed
Jelly-Fisher-fish opened this issue Nov 24, 2022 · 6 comments
Assignees

Comments

@Jelly-Fisher-fish
Copy link

Jelly-Fisher-fish commented Nov 24, 2022

harbor upgraded from v2.0 to v2.6.2

It failed to pull some artifacts with error response unknown: artifact

But i actually found it from db and web ui

What went wrong with docker pull

Error response from daemon: unknown: artifact projectname/imagename:v3-centosrepo_cve_fix not found

image

What went wrong with ctr image pull

ctr: failed to resolve reference "xxx/projectname/imagename:v3-centosrepo_cve_fix": xxx/projectname/imagename:v3-centosrepo_cve_fix: not found

image

Data in db

image

Data in web ui

image

And it can pull with digest

image

@chlins
Copy link
Member

chlins commented Nov 28, 2022

Could you try to execute the sql select * from repository where name like 'projectName/imageName'; in the database?

@chlins
Copy link
Member

chlins commented Nov 28, 2022

Maybe related with #17544

@Jelly-Fisher-fish
Copy link
Author

Maybe related with #17544

I tried once before created this issue, and only one repository as the result.

select * from repository where name like 'projectName/imageName';

image

@chlins
Copy link
Member

chlins commented Nov 28, 2022

Could you try to do this workaround #17544 (comment)?

@chlins chlins self-assigned this Nov 28, 2022
@Jelly-Fisher-fish
Copy link
Author

Jelly-Fisher-fish commented Nov 28, 2022

Could you try to do this workaround #17544 (comment)?

Step 1. Backup data
Step 2. docker run --rm firstfloor/before_reindex:latest --dburl=postgres://postgres:root123@localhost:5432/registry --command=list
Response with No duplicate repository name found!
Step 3. docker run --rm firstfloor/before_reindex:latest --dburl=postgres://postgres:root123@localhost:5432/registry --command=fix
Response with
No duplicate repository name found! Fix done! please run this command in database: REINDEX TABLE repository;
Step 4. REINDEX TABLE repository;
After try it all, I can pull the repository with tag
Thanks for your advice and response !

@Jelly-Fisher-fish
Copy link
Author

Maybe I can just run step 3 and 4 to fix it.
Now my problem is solved
Thanks for a lot

@chlins chlins closed this as completed Dec 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants