Replies: 1 comment 1 reply
-
|
Thanks for your report. I couldn't replicate it locally. What is set in TRIVY_IGNOREFILE on GitLab? Since the condition is determined by whether the file extension is
Also, did you mask [MASKED] manually, or was it automatically done by GitLab? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Description
I noticed an interesting bug after updating to 0.68.1 which has been hard to reproduce. We have GitLab CI pipelines which run Trivy with TRIVY_IGNOREFILE set to
.trivyignore.yaml. Both are running Trivy 0.68.1 but it works locally using ARM64 and fails remotely on x86.In all cases,
cat $TRIVY_IGNOREFILEproduces the expected contents and in the local tests I was literally copy-and-pasting from the failing CI job's output into my local file to confirm that it worked.What's interesting is that when it runs in the CI environment, it logs
DEBUG Found an ignore file file_path="[MASKED]"before failing but when it works locally it logsDEBUG Found an ignore yaml file_path=".trivyignore.yaml". Since that file exists and there are no errors logged, this makes me wonder whether there's some kind of silent failure when loading it which causes it to see the YAML file as not containing any keys for ignored CVEs.Desired Behavior
Actual Behavior
Reproduction Steps
TBD - even running locally with the same environmental variables does not fail so I'm trying to track down other environmental dependencies.Target
None
Scanner
None
Output Format
None
Mode
None
Debug Output
Operating System
aquasec/trivy container on Linux (fails) / native build passes MacOS Sonoma
Version
Checklist
trivy clean --allBeta Was this translation helpful? Give feedback.
All reactions