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

Allow InitContainer to pull vulnerability-db from private registry #2221

Open
crtvmn opened this issue Aug 9, 2024 · 0 comments
Open

Allow InitContainer to pull vulnerability-db from private registry #2221

crtvmn opened this issue Aug 9, 2024 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@crtvmn
Copy link

crtvmn commented Aug 9, 2024

Hello,

I'm trying to deploy the Trivy Operator in standalone mode with the provided Helm chart in an offline environment with a private registry. Credentials are required to access this registry.

Unfortunately, it is not possible to forward or add env variables (TRIVY_USER and TRIVY_PASSWORD) to allow the Trivy init-container to pull the vulnerability database from my private registry.

Moreover the dbRepositoryPassword and dbRepositoryUsername seem useless.

dbRepositoryUsername: ~
# -- The password for dbRepository authentication
#
dbRepositoryPassword: ~

Can you confirm that this use case is not possible for the moment? I found this discussion #1341 but no answer and no link to the related issue. Thanks for your help!

Best regards

@crtvmn crtvmn added the kind/bug Categorizes issue or PR as related to a bug. label Aug 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

1 participant