-
Notifications
You must be signed in to change notification settings - Fork 12
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
not able to use the nexus yum proxy repo to trivy #23
Comments
Still relevant issue in v0.38.3 |
Need fix repo metadata format (without hardcode github url) for proxy via nexus. |
@knqyf263 Would it be possible to get an update on this? |
@afdesk Would you look into it? |
oh, sorry guys. i missed this thread. |
@michael-brown-22 can i ask you to test the solution? I've built a demo rpm trivy repository and deployed it here https://trivy-repo-dev.github.io/ |
Hi, i have created a new yum proxy repo inside our nexus and pointed it to https://trivy-repo-dev.github.io/rpm/releases/7/x86_64/ Then when i do a yum install it fails with below error but if i use a standalone yum repo as below , it works fine |
@hjrrao |
my thoughts are next: before v0.37 the artifacts were stored in the same place with rpm metadata. your nexus instance can download the metadata, but can't find the artifact on github https://github.com/aquasecurity/trivy/releases/download/ |
Hello @afdesk, We have the same issue with nexus proxy repo. If I user baseurl=https://aquasecurity.github.io/trivy-repo/rpm/releases/8/x86_64/ the trivy latest package will get downloaded. But with proxy URL we are getting errors. Can you look into issue #34 any fix for this issue. |
Hi,
we have a nexus yum proxy repo pointing to https://aquasecurity.github.io/trivy-repo/rpm/releases/7/x86_64/
this is a part of a repository group in nexus.
On the nodes we are referencing that repo group in yum.repos.d files to install the packages.
This was working till last week.
from the last week, once the trivy was updated to 0.37, our yum install trivy command is not working and getting the error as in the image.
somehow the path v0.37.1 getting into the uri part . pls look at the attachment. any help is appreciated.
The text was updated successfully, but these errors were encountered: