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

Mitigate rate limit issues by utilizing mirror.gcr.io as default DB repository #7938

Closed
knqyf263 opened this issue Nov 18, 2024 · 1 comment · Fixed by #7679
Closed

Mitigate rate limit issues by utilizing mirror.gcr.io as default DB repository #7938

knqyf263 opened this issue Nov 18, 2024 · 1 comment · Fixed by #7679
Milestone

Comments

@knqyf263
Copy link
Collaborator

Description

The Trivy team has been exploring solutions to address the rate limit issues encountered during database updates and has provided some workarounds. It has come to our attention that mirror.gcr.io functions as a mirror for Docker Hub without imposing rate limits. By configuring mirror.gcr.io as the default repository for the Trivy databases, we can potentially resolve the current rate limit challenges. Additionally, incorporating GHCR as a secondary repository could provide further redundancy and reliability.

For reference, please see the related discussion

@DmitriyLewen
Copy link
Contributor

Added in #7679

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