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.

Sign up for GitHub

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

Jump to bottom

Cannot Use Nexus 3 Docker Registry #44

Closed
schrieveslaach opened this issue Jun 3, 2020 · 1 comment
Closed

Cannot Use Nexus 3 Docker Registry #44

schrieveslaach opened this issue Jun 3, 2020 · 1 comment
Labels
bug Something isn't working

Comments

@schrieveslaach
Copy link
Contributor

schrieveslaach commented Jun 3, 2020 •
edited
Loading

Currently, PREvant works with registry:v2 but pulling meta information from Docker registries that are hosted on Nexus do not work. It seems like that content negotiation of the registry client dkregistry needs to send the Accept header.

If I access the manifest resoure of a image with curl, the Content-Type is set to application/vnd.docker.distribution.manifest.v1+json:

curl -v https://registry.host/v2/user/image/manifests/v2 
* ...
< Content-Type: application/vnd.docker.distribution.manifest.v1+json

In contrast with an explicit Accept header the Content-type is set to application/vnd.docker.distribution.manifest.v2+json
@schrieveslaach schrieveslaach mentioned this issue Jun 3, 2020
Open
@schrieveslaach schrieveslaach added the bug Something isn't working label Jun 3, 2020
@schrieveslaach
Copy link
Contributor Author

The issue is related to Nexus 3 itself because it does not support q-factor weighting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@schrieveslaach