Fix /tmp/modsecurity/* directories permissions so nginx workers can write to them #300
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
theseion
approved these changes
Nov 7, 2024
|
Thanks! |
|
Release is building now. The new image will be available in a couple of hours. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hello,
We've noticed these errors in the logs:
The important bit is
Multipart: Failed to create file, whileMultipart: Final boundary missingis the consequence of that and is not the cause, but the effect of the issue.This PR changes the ownership on /tmp/modsecurity from root:root to nobody:nobody recursively, so nginx workers running under that user can write to the directories within /tmp/modsecurity.