Revert "nginx.conf: Use equal values for client_body_buffer_size and client_max_body_size to avoid writing big files to disk" #29
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Revert commit 4159eb5 due to nginx.conf already specifying a client_max_body_size that conflicts with the newly specified one.
In fact, client_max_body_size is set to
0
, disabling any limits, therefore preventing the registry from responding with 413 when a client tries to upload large layers.This needs further investigation to determine how Docker behaves with various registry settings, but in the meantime this needs to be reverted.
Change-Type: patch
Connects-To: #8
See: #28
HQ: https://github.com/resin-io/hq/issues/1115
---- Autogenerated Waffleboard Connection: Connects to #8