SPARK-43166: name docker users #40798
Closed
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
Member
|
@DerekTBrown Mind creating a JIRA and add it to the PR title please? See also https://spark.apache.org/contributing.html |
DerekTBrown
changed the title
Member
|
@DerekTBrown I have an alternative solution #40831, which should cover your case |
Author
|
Looks good. Closing in favor of #40831 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What changes were proposed in this pull request? / Why are the changes needed?
185, but no corresponding entry exists in/etc/passwd. This causes issues when libraries try to fetch the current unix username.useraddfunction as part of theDockerfile, to ensure that a name exists for these users.Does this PR introduce any user-facing change?
How was this patch tested?