Closed aqua-bot closed 4 days ago
Still seeing this in 0.57.1
Hello @sblatnick
Can you try to clear cache? (trivy clean --scan-cache
)
This command worked for me. Thanks!
(I thought we had tried this, but looks like either we the command never ran when we thought it did or maybe trivy clean --all
doesn't include the scan cache.)
hm... trivy clean --all
includes clearing of scan cache.
But anyway, it's good that Trivy now works properly.
Mystery solved. We discovered the real problem was we needed to specify the --cache-dir
like we do when we use trivy. For my local test, the default worked. But when we tried in our CI/CD tools, we use a custom path for a cache volume in kubernetes.
Backport
This will backport the following commits from
main
torelease/v0.57
: