sameersbn / sameersbn/docker-gitlab
Image registry error when layer is larger than 1GB
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
The docker push failed when the layer is larger than 1 GB.
Storage is set to S3 (MinIO). The chunk size has been increased.
REGISTRY_STORAGE_S3_CHUNKSIZE: 514288000
I see that during upload the size of the root disk under GitLab is reduced. Probably the tmp file is placed in /var/lib/nginx/body.
Is there a way to set the proxy_request_buffering variable in the gitlab-registry nginx conf file?
GitLab version: 16.3.0 (sameersbn/gitlab:16.3.0)
Registry version: registry:2.8.2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the gitlab-registry nginx configuration and the /var/lib/nginx/body path mentioned in the report. Reproduce a push with a layer larger than 1 GB using the stated S3 and chunk-size settings, then confirm that request buffering can be configured without exhausting the root disk.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, gitlab, nginx
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100