[SPARK-40864] Remove pip/setuptools dynamic upgrade #17
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.
What changes were proposed in this pull request?
Remove pip/setuptools dynamic upgrade in dockerfile
Why are the changes needed?
According to official image suggestion,
Rebuilding the same Dockerfile should result in the same version of the image being packaged.But we used to upgrade pip/setuptools to latest, actually we don't need a latest pip/setuptools for any reason I can think out. I also take a look on initial commits for this line, according merge history no more reason for it.
Does this PR introduce any user-facing change?
The OS recommand pip/setuptools version is used.
How was this patch tested?
CI passed.