Install Helix Python packages into a venv in a separate docker stage #1142
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
|
I've validated that installing the packages into an activated venv does not break the dotnet/runtime CI in dotnet/runtime#105157. |
|
Thanks! So much better! |
richlander
approved these changes
Jul 22, 2024
mthalman
reviewed
Jul 22, 2024
mthalman
approved these changes
Jul 22, 2024
|
Looks like there are issues with arm32. |
I thought that was the rule! |
…cker into venv-stage
3 tasks
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.
Install Helix python packages into a separate docker stage into a venv to avoid installing and uninstalling packages from the final image and to avoid using
--break-system-packages.