-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Getting Trivy version takes a long time #67121
Comments
Please note that Bitnami already released the latest version of Trivy at https://github.com/bitnami/containers/tree/main/bitnami/trivy. In this case, we need to wait until the upstream Harbor team cuts a new release for harbor-scanner-trivy bumping the bundled Trivy version. |
@carrodher
Aquasec
The solution is to release a new Bitnami |
That new harbor-adapter-trivy version was released yesterday, see aquasecurity/harbor-scanner-trivy#478. Our automated test and release pipeline detected the new version; however, we have identified some issues during the packaging process that require manual intervention. Our team is actively addressing these issues at the moment. We are committed to resolving them as quickly as possible. We will provide updates on this thread as soon as the new version is successfully released. |
I see. Thanks! |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Name and Version
bitnami/harbor-adapter-trivy:2.10.2-debian-12-r4
What architecture are you using?
amd64
What steps will reproduce the bug?
time trivy --version
What is the expected behavior?
The execution should be relatively fast (sub-secon) and the version is shown.
What do you see instead?
The version is shown but the execution takes seconds.
This is a problem because when Harbor calls this adapter -
/api/v1/metadata
, the scanner is marked as unavailable.Additional information
This issue concerns the slowness of the
version
subcommand aquasecurity/harbor-scanner-trivy#341.The issue seems to be fixed in
v0.51.1
.The text was updated successfully, but these errors were encountered: