-
Notifications
You must be signed in to change notification settings - Fork 8
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
handle larger volumes of data #10
Comments
I've been using registry:2 behind Nginx-proxy for 6months now. I never had any issues after setting
Can you try with |
it does work - I have used it like that for weeks.
My images are fairly large and I'm pushing them in parallel - I think there is some nginx setting which causes this.
… On 25. Jan 2020, at 17.02, Sudip Bhattarai ***@***.***> wrote:
I've been using registry behind Nginx-proxy for 6months now. I never had any issues.
blob upload unknown looks like an issue with the registry.
Can you try with docker run -d registry:2 instead and see if it works?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I also see this sometimes with eu.gcr.io - but I see it more when piping data through nginx-proxy now. I think the key is that I push 10 images in parallel which causes a lot of data being pushed and then some nginx (buffer?) runs low? |
Can you try modifying There are other settings mentioned available in Nginx documentation I don't know if it works, it's my random guess.
|
Hey @matti I have found two configuration changes that might solve the issue.
Furthermore, have you checked the file I have a WIP status in |
thanks, I try out soon! |
I opened #9 , which fixes the immediate problem, but I'm seeing
and
when I push to docker registry running behind the proxy.
What else needs to be configured larger?
The text was updated successfully, but these errors were encountered: