Skip to content
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

Request Entity Too Large #67

Closed
mangesj opened this issue Nov 1, 2019 · 1 comment
Closed

Request Entity Too Large #67

mangesj opened this issue Nov 1, 2019 · 1 comment

Comments

@mangesj
Copy link

mangesj commented Nov 1, 2019

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.

@StefanMadsen
Copy link

StefanMadsen commented Nov 18, 2019

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

more here:
https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/nginx-configuration/annotations.md

and heres more info :
kubernetes/ingress-nginx#1824

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants