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 code not compliant with docker specs #16515

Closed
alexmanno opened this issue Mar 11, 2022 · 10 comments
Closed

error code not compliant with docker specs #16515

alexmanno opened this issue Mar 11, 2022 · 10 comments
Assignees

Comments

@alexmanno
Copy link

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 of NOT_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:

$ docker-compose pull --ignore-pull-failures
Pulling nginx ... 
Pulling nginx ... done
Some service image(s) must be built from source by running:
    docker-compose build nginx

Against Harbor v2.3.0:

$ docker-compose pull --ignore-pull-failures
Pulling nginx ... 
Pulling nginx ... error
ERROR: for nginx  unknown: repository example/nginx-not-found not found
unknown: repository example/nginx-not-found not found

Same error as above but from curl:

Against Harbor v1.10.3:

{"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest unknown","detail":{"Tag":"example"}}]}

Against Harbor v2.3.0:

{"errors":[{"code":"NOT_FOUND","message":"repository example/foobar not found"}]}

Versions:
Please specify the versions of following systems.

  • harbor version: >= 2.1.0
  • docker engine version: 20.10.7
  • docker-compose version: 1.29.2
@github-actions
Copy link

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.

@github-actions github-actions bot added the Stale label May 18, 2022
@alexmanno
Copy link
Author

Hi @wy65701436, do you have any news on this?

@wy65701436 wy65701436 removed the Stale label May 19, 2022
@github-actions
Copy link

github-actions bot commented Jul 5, 2022

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.

@github-actions github-actions bot added the Stale label Jul 5, 2022
@alexmanno
Copy link
Author

Any news on this?

@github-actions github-actions bot removed the Stale label Jul 7, 2022
@github-actions
Copy link

github-actions bot commented Sep 6, 2022

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.

@github-actions github-actions bot added the Stale label Sep 6, 2022
@alexmanno
Copy link
Author

Any news on this?

@reasonerjt
Copy link
Contributor

Harbor will NOT implement Docker's spec, instead, the target is to be compliant with
https://github.com/opencontainers/distribution-spec/blob/main/spec.md

Therefore, seems we should return the error code NAME_UNKNOWN

@wy65701436

@reasonerjt reasonerjt added backlog and removed Stale labels Sep 6, 2022
@github-actions
Copy link

github-actions bot commented Nov 6, 2022

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.

@github-actions github-actions bot added the Stale label Nov 6, 2022
@Vad1mo
Copy link
Member

Vad1mo commented Nov 28, 2022

@Vad1mo Vad1mo closed this as completed Nov 28, 2022
@Vad1mo
Copy link
Member

Vad1mo commented Nov 28, 2022

I am closing the PR, feel free to reopen if you think we need to discuss that again.

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

4 participants