-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: cache trivy-test-images #7598
Comments
Hi @knqyf263, We started hitting this issue in our pipeline. What are your thoughts on this workaround? |
That was helpful @DmitriyLewen , thank you. This comment confirms my initial suspicion of this being a rate limit on the ghcr.io/aquasecurity/trivy repository: #7580 (comment) I'm thinking that we should go with |
If your image has java stuff in it, also add |
@veselov |
Description
Currently, we pull test images every time we run integration/module/VM tests on GitHub Actions.
trivy/magefiles/fixture.go
Line 35 in 8128ecc
trivy/magefiles/fixture.go
Line 89 in 8128ecc
These images are rarely changed and should be cached on GitHub Actions to mitigate 429 errors.
cf. https://github.com/aquasecurity/trivy/actions/runs/11045901509/job/30685527564
The text was updated successfully, but these errors were encountered: