-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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 code not compliant with docker specs #16515
Comments
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. |
Hi @wy65701436, do you have any news on this? |
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. |
Any news on this? |
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. |
Any news on this? |
Harbor will NOT implement Docker's spec, instead, the target is to be compliant with Therefore, seems we should return the error code |
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. |
Hello @alexmanno We checked your PR and we fear that this change would break the OCI spec. See: |
I am closing the PR, feel free to reopen if you think we need to discuss that again. |
If you are reporting a problem, please make sure the following information are provided:
Expected behavior and actual behavior:
When an image is not available on the registry, it should return
MANIFEST_UNKNOWN
error code instead ofNOT_FOUND
as described in https://docs.docker.com/registry/spec/api/#errors-2 .This unexpected error code seems as been introduced in version 2.1.0. (#12006)
This unexpected error brokes
docker-compose pull --ignore-pull-failures
. In fact it should exit without errors but it exit with an error instead.Steps to reproduce the problem:
Both tests are executed with a non existent image
Against Harbor v1.10.3:
Against Harbor v2.3.0:
Same error as above but from curl:
Against Harbor v1.10.3:
Against Harbor v2.3.0:
Versions:
Please specify the versions of following systems.
The text was updated successfully, but these errors were encountered: