We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Tried with several images, all crash with panic: runtime error: invalid memory address or nil pointer dereference
panic: runtime error: invalid memory address or nil pointer dereference
Using docker-index_0.0.13_windows_amd64 on powershell with a 16GB i5
docker-index_0.0.13_windows_amd64
This one from public docker repository
.\docker-index cve --image mcr.microsoft.com/dotnet/runtime:5.0-focal DSA-2022–0001
full stack trace
level=info msg="Requesting image mcr.microsoft.com/dotnet/runtime:5.0-focal" level=info msg="Copied image" INFO Indexing ⠋ panic: runtime error: invalid memory address or nil pointer dereference [signal 0xc0000005 code=0x0 addr=0x30 pc=0x1d11f68] goroutine 75 [running]: github.com/aquasecurity/trivy/pkg/fanal/artifact/image.Artifact.Inspect({{0x0, 0x0}, {0x1ce46cc5358, 0xc003fbba88}, {{{0x0, 0x0, 0x0}, {0xc002c3c500, 0x3, 0x4}}}, ...}, ...) /home/runner/go/pkg/mod/github.com/aquasecurity/trivy@v0.30.4/pkg/fanal/artifact/image/image.go:72 +0x68 github.com/docker/index-cli-plugin/sbom.trivySbom({0xc002c60140, 0x9b}, {0xc003d14720, 0xc003d14750, 0xc003d147e0, 0xc003d14780, 0xc003d147b0}, 0xc003ac8c60) /home/runner/work/index-cli-plugin/index-cli-plugin/sbom/trivy.go:67 +0x363 created by github.com/docker/index-cli-plugin/sbom.indexImage /home/runner/work/index-cli-plugin/index-cli-plugin/sbom/index.go:95 +0x40f
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Tried with several images, all crash with
panic: runtime error: invalid memory address or nil pointer dereference
Using
docker-index_0.0.13_windows_amd64
on powershell with a 16GB i5This one from public docker repository
full stack trace
The text was updated successfully, but these errors were encountered: