Trivy Scanner Failures in Trunk Check (Multiple Versions)

[vtsachev]

Users have reported failures when running trunk check, specifically related to the Trivy scanner exiting with code 1. The error appears to be related to missing policy files within the Trivy cache, leading to scan initialization failures.

Reported Behavior:

• Trivy exits with exit_code=1 when scanning configurations.
• Error message indicates a failure in initializing the filesystem scanner due to missing policy files.
• The issue persists across multiple attempts and may present different missing policy files across runs.
• In some cases, clearing the Trivy and Trunk cache has temporarily resolved the issue, but new errors emerge.
• Affected users include those running both CI and local environments.
• Related reports indicate upstream issues in the Trivy repository.

User Reports:

• Dec 16, 2024: Initial report from a user encountering a failure in trunk check with Trivy exiting unexpectedly. (Trivy version 0.56.2, Trunk CLI 1.22.7)
• Dec 17, 2024: After attempting cache cleaning, the user reported new errors appearing in Trivy scans. (Trivy version 0.56.2, Trunk CLI 1.22.7)
• Dec 18, 2024: The issue was temporarily resolved by reverting to trunk_cli_version 1.22.7 and cleaning caches.
• Jan 15, 2025: Multiple new reports surfaced with similar failures, indicating an ongoing problem. (Trivy version 0.56.2, Trunk CLI 1.22.7)
• Jan 16, 2025: A related upstream issue in Trivy was identified: GitHub Discussion #7139.
• Jan 21, 2025: Additional users confirmed experiencing this issue frequently. (Trivy version 0.56.2, Trunk CLI 1.22.7)