I face a problem where some of the images are in a private registry.
When I use the configuration for trivy where I set TRIVY_USERNAME,TRIVY_PASSWORD and TRIVY_AUTH_URL then trivy scans the images fine.
However it somehow looses capability to scan images on public docker/gcr/quay registries.
Have you seen this issue and found a solution for it?
To answer myself:
Mount the dockerconfigjson for the private registry into the kube-trivy-exporter pod to /root/.docker/config.json. Don't set any env vars.
This works fine for me.
Thanks for this great exporter!
I face a problem where some of the images are in a private registry. When I use the configuration for trivy where I set
TRIVY_USERNAME
,TRIVY_PASSWORD
andTRIVY_AUTH_URL
then trivy scans the images fine. However it somehow looses capability to scan images on public docker/gcr/quay registries.Have you seen this issue and found a solution for it?