-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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 the artifact is not ready yet, failed to tag it #18173
Comments
Did the pull command fail or just failed to create tag in the proxy cache project? From the error log I can not find any hint, could you add more log and error information in the command line?
|
This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days. |
This issue was closed because it has been stalled for 30 days with no activity. If this issue is still relevant, please re-open a new issue. |
Any news on this? Got the same issue today. When pulling e.g. library/node it gets listed and tagged but when I try pulling e.g. alpine/helm I got the following error message:
The pull works as expected but the tagging goes wrong and its not shown in the UI. |
This issue-14822 is not resolved
Bitnami Helm Chart:
16.3.0
App version:
2.7.0
This error is false, Harbor should be able to pull and cache these images but it fails
This is the error from harbor-core pod
Pulling and caching from private registry (quay.io) works fine
pulling (public) from DockerHub fails with the bellow errors:
(This error is false, Harbor should be able to pull and cache these images but it fails, This is the error from harbor-core pod)
The text was updated successfully, but these errors were encountered: