Closed zyyw closed 1 year ago
It is just a timeout like the log message says. Jar scanning takes time and it is likely to lead to a timeout. You need to increase the timeout value. https://github.com/aquasecurity/harbor-scanner-trivy/blob/ff073cd57730f9258ec9fb6a72852f61a598f6e4/helm/harbor-scanner-trivy/values.yaml#L69-L70
Notice also, that scanning certain images may required more memory than the other. Container images with Java applications are one example.
It could be another issue.
This issue is stale because it has been labeled with inactivity.
Hi, when running pipeline to prepare for Harbor 2.6.0 release (using TRIVYVERSION=v0.29.2, TRIVYADAPTERVERSION=v0.30.0), we found scan all occasionally failed (not consistent fails) with the following error message:
a relatively full message is here:
This error is similar to this one:
running trivy: signal: killed
while in this issue it isrunning trivy: exit status 1
.We noticed that there is comment in https://github.com/goharbor/harbor/issues/15977#issuecomment-1105161690, saying:
And from the log message, we can see that there is scanning against some
.jar
files. Could you please help to verify whether this two issues are more or less the same problem? Thanks