error `413 request entity too large` while pushing an image

See original GitHub issue

I am getting an error while pushing to ttl.sh, 413 request entity too large. https://github.com/waveywaves/backstage/actions/runs/3103852916/jobs/5027642820#step:16:661

Based on the docker documentation I understand that the following configuration is necessary to get around this issue https://docs.docker.com/registry/recipes/nginx/#setting-things-up

# disable any limits to avoid HTTP 413 for large image uploads
client_max_body_size 0;

Issue Analytics

State:
Created a year ago
Comments:10 (5 by maintainers)

Top GitHub Comments

5reactions

z4cecommented, Sep 30, 2022

I submitted a PR to fix this in the upstream buildx uses: https://github.com/containerd/containerd/pull/7459

2reactions

z4cecommented, Sep 30, 2022

Hi @kaovilai I spoke with @waveywaves on Kubernetes slack. I believe this because the buildx plugin is using the the push driver from containerd which apparently does not support transfer-encoding: chunked see: https://github.com/containerd/containerd/blob/main/remotes/docker/pusher.go#L265

The best workaround for now is just to use regular docker push instead of using buildx to push your image. I do see some other code in the buildx code for using a moby driver which might as well, but I’m not sure how to enable it through the github action.