-
Notifications
You must be signed in to change notification settings - Fork 551
-
Notifications
You must be signed in to change notification settings - Fork 551
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
grype db status
reports "valid" when the DB is missing
#2077
Comments
Possibly related to #1648 |
Thanks for the report; I've seen this along with other oddities in some of the database handling, since we've been looking at solving download issues users have reported, if I get around to rewriting bits of it, I'll try to make sure to address this stuff too. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened:
So far so good — and then...
What you expected to happen:
Some indication that the Grype DB is not valid — that it could not be verified because it could not be found.
How to reproduce it (as minimally and precisely as possible):
(See above)
Anything else we need to know?:
I don't expect this is a common scenario, FWIW. I got into this state while debugging another DB issue. But still, that this is possible seems not ideal.
Environment:
grype version
:cat /etc/os-release
or similar):The text was updated successfully, but these errors were encountered: