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
S3 Storage Fails with storage: read exceeds limit #4325
Comments
There is a read limit on pulls to prevent memory allocations ( distribution/registry/storage/io.go Line 13 in 5d5c60f
docker pull ?
|
Both using docker pull and FROM keyword, and also K8s pull using ContainerD |
I have searched for the error message (after storage: prefix but found nothing) |
As I see on code I think I was trying to make the image to be a single layer So it was exceeding that limit |
I would also recommend you to switch to |
Thanks |
It's not been marked as stable yet, but the changes have been accumulated over the past couple of years -- before we released v3 there had been no release for over 5 years. See the not-fully complete changelog here: https://github.com/distribution/distribution/releases/tag/v3.0.0-alpha.1 |
Thank you again Also I have some integrations with HTTP V2 API and Debug API |
Description
We are building an image based on
php:8.2-cli-bookworm
(using earthly)and our registry storage is S3, and we are able to push image without problem, but when we want to pull image we are getting
500: Internal Server error, with unknown error in log and in details we are getting
storage: read exceeds limit
Reproduce
Here is my Earthfile
Expected behavior
Pull image without problem
registry version
image tag:
registry:2
version:
registry github.com/docker/distribution 2.8.3
Additional Info
Image size is about 600 MBs
But there was nothing in directories related to this image/manifest in my S3 bucket
and
There is no problem while using Dockerfile (I think there are some problems with buildkit/earthly)
The text was updated successfully, but these errors were encountered: