Merged
Conversation
The mirror.gcr.io registry was returning 404 for the Trivy vulnerability DB artifact, breaking the Docker image scan job. Pin trivy-action to v0.28.0 and explicitly set TRIVY_DB_REPOSITORY to the primary ghcr.io source. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
aquasecurity/trivy-actionto@0.28.0instead of@masterfor stabilityTRIVY_DB_REPOSITORYtoghcr.io/aquasecurity/trivy-db:2to fix 404 errors frommirror.gcr.ioContext
The security scan was failing because
mirror.gcr.ioreturned a 404 when Trivy tried to download its vulnerability database. Theghcr.ioregistry is the primary source maintained by Aqua Security and is more reliable.Test plan
🤖 Generated with Claude Code