-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Cannot connect to Azure Container Registry #80
Comments
We scan ACR images on daily basis with no issues. I think the exception complains about your image name. |
hi @v1r7u - Thank you for your comment. I just tried to run a scan using the format you suggested and got a new error now; if you are able to run scans of ACR Images, do you have any environment variables set? How do you have it working? |
Try to update docker server version. We had similar problem with older one, but it works fine with How our process looks like
Note, we're mapping 2 volumes: one with docker socket, another with cache folder. With properly mapped docker.sock, if image is already in local docker cache, trivy does not need any environment variables with credentials. If image is not on machine, trivy would try to pull it using credentials in env.vars.
off-topThe problem with trivy - it's quite fragile. There is 100 and 1 ways of running it in a wrong way... The worst part, exceptions often are not self-explaining :) |
Almost as a reminder to myself... but running Trivy via docker on an image hosted by Azure's ACS looks like this -
You almost say that above, but it'd be nice to have a simple working example for that stupid cloud (not blaming you :)) (slight edit to put in newline between commands :( |
@divgo do you still have problems? Trivy actually dont have support for windows OS. |
This issue is stale because it has been labeled with inactivity. |
* Add check to test for surge_upgrade in DO Kubernetes clusters. * Use proper values in struct in Surge example. * Use singular form in struct. * Add documentation
It appears that Trivy cannot connect to a Container Registry hosted in Azure.
I have the following Environment Variables set on my local machine;
Whether I use http or https, I get the same error above.
The text was updated successfully, but these errors were encountered: