Skip to content
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

feat: support multiple DB repositories for vulnerability and Java DB #7603

Closed
knqyf263 opened this issue Sep 26, 2024 · 0 comments · Fixed by #7605
Closed

feat: support multiple DB repositories for vulnerability and Java DB #7603

knqyf263 opened this issue Sep 26, 2024 · 0 comments · Fixed by #7605
Assignees
Milestone

Comments

@knqyf263
Copy link
Collaborator

Background

Currently, the vulnerability database repository is controlled by the --db-repository flag, with the default value set to ghcr.io/aquasecurity/trivy:2. Due to recent instability issues with GHCR, we have published an identical DB to ECR Public. We need to update Trivy to support multiple repository options to improve reliability and provide alternatives.

Proposed Changes

  1. Modify the --db-repository flag to accept multiple values:

    • Change from --db-repository string to --db-repository strings
    • Trivy should try repositories one by one until successful
    • Set default values to include both GHCR and ECR Public repositories
  2. Apply the same changes to the Java DB configuration

  3. Ensure backward compatibility:

    • The flag should still accept a single value to avoid impacting existing users

Out of Scope

  • Changes to the checks bundle are not included in this issue, as it contains embedded checks. The necessity for similar modifications will be discussed separately.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

2 participants