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

Handle unsupported docker image types better #5151

Open
tas50 opened this issue Feb 1, 2025 · 0 comments
Open

Handle unsupported docker image types better #5151

tas50 opened this issue Feb 1, 2025 · 0 comments

Comments

@tas50
Copy link
Member

tas50 commented Feb 1, 2025

Describe the bug
If the go-containerregistry library can't handle an old manifest it throws the user a warning with a link to their repo. We should catch these and throw our own warning.

cnspec scan docker image nginx:1.7.11 --config ~/Downloads/edge-default.json
→ loaded configuration from /Users/tsmith/Downloads/edge-default.json using source --config
→ using service account credentials
→ discover related assets for 1 asset(s)
x unable to create runtime for asset error="rpc error: code = Unknown desc = unsupported MediaType: \"application/vnd.docker.distribution.manifest.v1+prettyjws\", see https://github.com/google/go-containerregistry/issues/377" asset=
Asset: ()
----------

error: rpc error: code = Unknown desc = unsupported MediaType: "application/vnd.docker.distribution.manifest.v1+prettyjws", see https://github.com/google/go-containerregistry/issues/377


Scanned 1 asset
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