Introduce CHOWN_FILES_ON_STARTUP env var, which defaults to 1 but can be disabled #81
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
|
This feature would be very useful for me too! |
|
Actually in my use case i have solved this issue adding :ro to the docker volume! |
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.
I have a use case where it makes perfect sense to mount a read-only filesystem, as-is, and make no changes to ownership at the start of the container. I didn't want to change default behavior for everybody else, though! So I added an environment variable which allows for chowning to be an optional - but default - behavior. Anyone who needs to turn chowning off, they can.