Repository navigation
Replies: 0 comments
|
You're right, that limit was hardcoded, and it was also wrong. Drydock collected up to 50 MB of Trivy output and then refused to parse anything over 20 MB, so a report like yours (40 MB) was captured and thrown away. Fixed in #1359. There's one limit now, it's 64 MB by default, and you can raise it: It takes a byte count from 1 MB to 1 GB. Your uptime-kuma scan fits under the new default, so you shouldn't need to set anything. If an image does go over, the error names the variable. That's in |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Currently, one of my containers is failing because the dependency tree is too large. I saw that MAX_TRIVY_PARSE_BYTES is hardcoded. Is there any way we could either increase that value or make it configurable?
Here is the error I am running into:
All reactions