Gcp fix filesystem table #1305
Merged
Gcp fix filesystem table #1305
+7
−9
Conversation
This file contains hidden or 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
The nginx master process, like the worker process, can write to /spool/nginx and /var/spool/nginx. This also removes the /var/log/nginx row which we don't want to advertise as scratch space for the user because the contents of that directory can get exported to google cloud logging.
github-actions
bot
added
the
documentation
✅ Deploy Preview will be available once build job completes!
|
ornj
approved these changes
Oct 14, 2025
UnwashedMeme
approved these changes
Oct 14, 2025
pdabelf5
pushed a commit
that referenced
this pull request
Oct 22, 2025
fix n4g filesystem restrictions table and remove multiple of 10 NCU constraint
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.
Proposed changes
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩