You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using clairctl to create reports from the Clair image analysis, also performed using clairctl. The report issued for a compromised image is information-rich, showing the number of vulnerabilities found and describing each one of it. However, reposrts issued for "clean images" does not show information like "no vulnerabilities found".
Bad Report:
Good Report:
I'm missing the "Total: 0 Vulnerabilities: 0" on the bad report.
Is this expected or am I doing something wrong?
PS: Using 2.0.1
Thanks!
Paulo
The text was updated successfully, but these errors were encountered:
Clair need to sync the security data from the NVD and parse those meta data save into postgres DB.
If you postgres DB is null. the report will show "no vulnerabilities found".
I don't think this is the problem. I use the same database to perform analysis on other images. My point here is not the lack of vulnerabilities OR the scanning quallity, but the absense of "Total: 0 Vulnerabilities" text on the report for a scanned image with no issues.
The lack of this piece of information make report interpretation unclear as I'm able to see only image SHA and the repository/image name.
Hi,
I'm using clairctl to create reports from the Clair image analysis, also performed using clairctl. The report issued for a compromised image is information-rich, showing the number of vulnerabilities found and describing each one of it. However, reposrts issued for "clean images" does not show information like "no vulnerabilities found".
Bad Report:
![bad-report](https://user-images.githubusercontent.com/32147428/44052914-6fb0a092-9f14-11e8-855a-0dc8ef698b18.jpg)
Good Report:
![good-report](https://user-images.githubusercontent.com/32147428/44052915-6fd58aba-9f14-11e8-8c43-c58dc2efa643.jpg)
I'm missing the "Total: 0 Vulnerabilities: 0" on the bad report.
Is this expected or am I doing something wrong?
PS: Using 2.0.1
Thanks!
Paulo
The text was updated successfully, but these errors were encountered: