[BUG] Trivy fails to scan Docker image: INTERNAL_ERROR; received from peer
#5345
Replies: 2 comments
-
I have the sae and here is my log for run with trivy --reset: trivy image --reset && trivy image debezium/connect:1.9.0.Final --ignore-unfixed -d -v 2023-10-05T19:55:31.508+0200 INFO Removing DB file...
|
Beta Was this translation helpful? Give feedback.
-
Created #5440 for this issue. |
Beta Was this translation helpful? Give feedback.
-
Description
Hello, I've encountered an issue with scanning a few images that ended up with
INTERNAL_ERROR
.The image is publicly available
debezium/connect-base:1.9
. This problem happens once every few scans, i.e. the same commands executed right after this failure, ended up with a success and a proper report. We've also encountered similar problems with a few other images as wellDesired Behavior
Scan always ends with a proper report
Actual Behavior
Sometimes scan fails
Reproduction Steps
Target
Container Image
Scanner
Vulnerability
Output Format
None
Mode
None
Debug Output
Operating System
MacOS Sonoma 14.0 (but this also happens on K8s, via trivy-operator)
Version
Checklist
trivy image --reset
Beta Was this translation helpful? Give feedback.
All reactions