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
You can utilize `make db-all` to build the database, the DB artifact is outputted to the assets folder.
As far as I can tell, the target was removed in commit 6121d35. I was going to work around it by just building the docker image instead with docker build . -t trivy-db, but that references make db-all also, which implies it doesn't work at all and probably isn't used in general.
The CI file uses the db-build target instead but the README has no instructions for setting up your dev environment to make that actually work locally.
Is there another target we should use? Experimentally, I can get it working by recreating what that old deleted target was doing but I'm not sure why I would have to do that.
For context, I'm just trying to build the db to work around the rate limiting issues described in aquasecurity/trivy-action#389
The text was updated successfully, but these errors were encountered:
Are the docker and public.ecr.aws repos fair game for the public to use as well? Compared to the ghcr repo they're very underutilized. If I can just add --db-repository public.ecr.aws/aquasecurity/trivy-db:2 to my trivy command and get my images from a non ghcr source then that's probably much easier, unless the AWS one isn't updated as often or has some other issue.
The docs say that you can build the trivy db by checking out the repo and running
make db-all
.trivy-db/README.md
Line 52 in e76bad9
As far as I can tell, the target was removed in commit 6121d35. I was going to work around it by just building the docker image instead with
docker build . -t trivy-db
, but that referencesmake db-all
also, which implies it doesn't work at all and probably isn't used in general.The CI file uses the
db-build
target instead but the README has no instructions for setting up your dev environment to make that actually work locally.trivy-db/.github/workflows/cron.yml
Lines 43 to 44 in e76bad9
Is there another target we should use? Experimentally, I can get it working by recreating what that old deleted target was doing but I'm not sure why I would have to do that.
For context, I'm just trying to build the db to work around the rate limiting issues described in aquasecurity/trivy-action#389
The text was updated successfully, but these errors were encountered: