You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 21, 2022. It is now read-only.
Running trivy in debug mode on an OCI image I ran across the error message:
unexpected media type: application/vnd.oci.image.layer.v1.tar for layer: sha256:
The stack trace pointed to docker.go:220, where I lost the trail for the moment since it's now calling an interface method and I didn't have the time to work out the runtime type at play. Note that docker.go has been refactored since this commit a few weeks ago.
Running trivy in debug mode on an OCI image I ran across the error message:
The stack trace pointed to docker.go:220, where I lost the trail for the moment since it's now calling an interface method and I didn't have the time to work out the runtime type at play. Note that docker.go has been refactored since this commit a few weeks ago.
I noticed that application/vnd.oci.image.layer.v1.tar+gzip is explicitly part of the test suite, but not application/vnd.oci.image.layer.v1.tar. It does look like uncompressed image layers are supported by the underlying library - see OCIUncompressedLayer vs OCILayer in go-containerregistry:/pkg/v1/types/types_test.go.
Here's the full debug output in case it's interesting at all. Trivy version is 0.8.0, run with an OCI image created with this command:
The text was updated successfully, but these errors were encountered: