Dockerfile: Fixed file permissions for media #276
Merged
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
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.
Related Issue: #252
New Behavior
In case a container is executed with an arbitrary user id (e.g. "101" like in docker-compose.yml), Netbox has write permissions for all media folders (devicetype-images, image-attachments).
Contrast to Current Behavior
Netbox cannot create files inside devicetype-images and image-attachments if container's uid is not 0.
Discussion: Benefits and Drawbacks
Benefits:
Drawbacks:
Changes to the Wiki
None
Proposed Release Note Entry
Dockerfile: Fixed file permissions for media folders
Double Check
developbranch.