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

Scanner is not working for Harbor Proxy Cache Projects #115

Open
gilAqua opened this issue Jan 23, 2023 · 0 comments
Open

Scanner is not working for Harbor Proxy Cache Projects #115

gilAqua opened this issue Jan 23, 2023 · 0 comments

Comments

@gilAqua
Copy link

gilAqua commented Jan 23, 2023

When the Aqua Harbor Scanner plugin scans a proxy cache image, it fails to send a tag value to the Aqua Scanner. This results in the Scanner using ":latest" as the tag. This results in image scan failure because there may not be a ":latest" tagged image.

Example :

"artifact": {
"namespace_id": 3,
"repository": "ext.hub.docker.com/library/node",
"tag": "",
"digest": "sha256:26c00e8ca7cbe467e35d4efdbe3aded834b0b7bf7512d62db4c51f6b86466e1c",
"mime_type": "application/vnd.docker.distribution.manifest.v2+json"

Since ":latest" is appended automatically due to the missing value for tag, the scanner fails with:

Failed scanning image ext.hub.docker.com/library/node::latest: image was not found in registry
: general response handler: unexpected status code: 500, expected: 200

It seems the Adapter needs to parse the tag information from the source image data differently than it is currently doing for Proxy Cache. There is something different about how Harbor and/or this Scanner Adapter is able to handle the image tags.

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

1 participant