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
We've currently got Aqua Helm chart running console and a scanner, but when scanning a particular image locally from my Mac command line, we're getting the error
"twirp error unknown: Error from intermediary with HTTP status code 413 "Request Entity Too Large""
The image is 1.4gb.
The confusing factor in this, is that when scanning the same image from the console, it works fine.
The text was updated successfully, but these errors were encountered:
I had a similar issue, - this was due to a ingress controller not allowing "large" payloads.
Our nginx ingress controller reads annotations and could be set via our helm install with set commands:
--set web.ingress.annotations."nginx.ingress.kubernetes.io/client-body-buffer-size"="[size you need]"
--set web.ingress.annotations."nginx.ingress.kubernetes.io/proxy-body-size"="[size you need]"
it most likely depends on your loadbalancer/ingress
We've currently got Aqua Helm chart running console and a scanner, but when scanning a particular image locally from my Mac command line, we're getting the error
"twirp error unknown: Error from intermediary with HTTP status code 413 "Request Entity Too Large""
The image is 1.4gb.
The confusing factor in this, is that when scanning the same image from the console, it works fine.
The text was updated successfully, but these errors were encountered: