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.

Sign up for GitHub

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

Jump to bottom

413 Request Entity Too Large with mirror-registry 2.0.3 #179

Open
apodhrad opened this issue Nov 29, 2024 · 5 comments
Open

413 Request Entity Too Large with mirror-registry 2.0.3 #179

apodhrad opened this issue Nov 29, 2024 · 5 comments

Comments

@apodhrad
Copy link

apodhrad commented Nov 29, 2024 •
edited
Loading

When pushing big images to quay installed by mirror-registry 2.0.3 I'm getting this error

413 Request Entity Too Large

Note that this is working with mirror-registry 1.3.5. I will try also other versions.

EDIT: it is working also with 1.3.10
@HammerMeetNail
Copy link
Contributor

Hey @apodhrad, What is the size of the size of the image? Are you able to share it so we can try to recreate?

@LiZhang19817
Copy link

LiZhang19817 commented Dec 2, 2024 •
edited
Loading

@apodhrad We tried to reproduce this issue as you mentioned, but when pushing image with large layer size "9.4GB", can't reproduce this issue, is it possible to share your image to confirm.

$ ./mirror-registry --version

   __   __
  /  \ /  \     ______   _    _     __   __   __
 / /\ / /\ \   /  __  \ | |  | |   /  \  \ \ / /
/ /  / /  \ \  | |  | | | |  | |  / /\ \  \   /
\ \  \ \  / /  | |__| | | |__| | / ____ \  | |
 \ \/ \ \/ /   \_  ___/  \____/ /_/    \_\ |_|
  \__/ \__/      \ \__
                  \___\ by Red Hat
 Build, Store, and Distribute your Containers

mirror-registry version v2.0.3

podman push quayomr.qe.devcluster.openshift.com:8443/quay/test123 --tls-verify=false --creds quay:***
Getting image source signatures
Copying blob 2653d992f4ef done   | 
Copying blob 637a3c7a75fa [===>----------------------------------] 1.1GiB / 9.4GiB | 260.1 MiB/s

podman push quayomr.qe.devcluster.openshift.com:8443/quay/test123 --tls-verify=false --creds quay:***
Getting image source signatures
Copying blob 2653d992f4ef done   | 
Copying blob 637a3c7a75fa done   | 
Copying config 76e8b2c5c2 done   | 
Writing manifest to image destination

@LiZhang19817
Copy link

@apodhrad We want to know if you hit the same error as following example.

podman push quayomr.qe.devcluster.openshift.com:8443/quay/ai --tls-verify=false --creds quay:***
Getting image source signatures
Copying blob aa81dcfd55ea [=========================>------------] 20.0GiB / 29.5GiB | 167.9 MiB/s
Copying blob 24b5ce0f1e07 done   | 
Error: writing blob: uploading layer chunked: StatusCode: 413, "<html>\r\n<head><title>413 Request Entity Too Large<..."

@apodhrad
Copy link
Author

apodhrad commented Dec 2, 2024

Hi @LiZhang19817 I hit exactly the same error.
Unfortunately, today with a fresh install I was not able reproduce it :(

@LiZhang19817
Copy link

LiZhang19817 commented Dec 3, 2024 •
edited
Loading

@apodhrad Is it possible to share your test image then we can see if it's the same issue.
Actually there's a config "MAXIMUM_LAYER_SIZE", the default largest layer size is 20GB
https://docs.redhat.com/en/documentation/red_hat_quay/3.13/html-single/configure_red_hat_quay/index#config-fields-storage-fields

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@HammerMeetNail @apodhrad @LiZhang19817