Explicit UID Instructions #4391
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
ghogen
reviewed
Mar 12, 2021
ghogen
approved these changes
Mar 12, 2021
Co-authored-by: Gordon Hogenson <[email protected]>
This was referenced Mar 16, 2021
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.
Thanks once again to @TheYarin for giving us great feedback to improve the product! We have now changed our Python scaffolding to include the best practice of setting an explicit UID when creating a non-root user.
We changed our docs to Bash rather than powershell.
Lastly, we updated our instructions to help the user setfacls from their host with the knowledge that they already have an explicit UID declared