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.

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

Open
matti opened this issue Jan 25, 2020 · 6 comments
Open

handle larger volumes of data #10

matti opened this issue Jan 25, 2020 · 6 comments

Comments

@matti
Copy link

matti commented Jan 25, 2020

I opened #9 , which fixes the immediate problem, but I'm seeing

441e28f31fd7: Retrying in 1 second

and

blob upload unknown

when I push to docker registry running behind the proxy.

What else needs to be configured larger?

@mesudip
Copy link
Owner

mesudip commented Jan 25, 2020

I've been using registry:2 behind Nginx-proxy for 6months now. I never had any issues after setting client_max_body_size=2g.

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?

@matti
Copy link
Author

matti commented Jan 25, 2020 via email

@matti
Copy link
Author

matti commented Jan 27, 2020

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?

@mesudip
Copy link
Owner

mesudip commented Jan 28, 2020

Can you try modifying proxy_buffering off; inside http{ ...} in /etc/nginx/nginx.conf file?

There are other settings mentioned available in Nginx documentation

I don't know if it works, it's my random guess.
The command I use is

docker cp <nginx-container>:/etc/nginx/nginx.conf nginx.conf
vim nginx.conf  # then edit the file
docker cp nginx.conf <container-name>:/etc/nginx/nginx.conf
docker exec  <container-name> nginx -s reload 

@mesudip
Copy link
Owner

mesudip commented Feb 27, 2020

Hey @matti I have found two configuration changes that might solve the issue.

proxy_buffering off; 
proxy_request_buffering off;

Furthermore, have you checked the file /var/log/nginx/error.log in the container? It might contain the detail of the issue.

I have a WIP status in mesudip/nginx-proxy:test that contains the above two configuration changes. Can you check it out?

@matti
Copy link
Author

matti commented Feb 27, 2020

thanks, I try out soon!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants