CI complains hitting rate limit on trivy scan

[ekneg54]

Expected behavior
the CI Containerbuilds should complete with trivy scan

Current behavior
sometimes they does not complete because of a rate limit.
this behavior is a known "bug" ... see: aquasecurity/trivy#7668

Steps to reproduce

• run ci pipeline frequently

Possible solution

• cache trivy db for 1 day in the pipeline to reduce requests

[ekneg54]

@P4sca1 could you have a look on that?

[P4sca1]

There is a Trivy PR which aims to solve this issue by providing additional fallback registries: aquasecurity/trivy#7679.

In the meantime, the following workaround might help: aquasecurity/trivy#7668 (reply in thread).

We are already caching the trivy db for one day, which should help after the first Trivy pipeline of the day succeeded.