Allowing developer set uv version when building task image #3234
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.
Tracking issue
uv --locked problem
Why are the changes needed?
Based on the feedback and tests, this problem is sparked by difference between the one in user side and the one in dockerfile.
My environment:
Ubuntu 24.04
x86_64
Experiment steps.
Results are following.
What changes were proposed in this pull request?
How was this patch tested?
building node image with specific uv.
4.1 export FLYTE_UV_VERSION=0.5.14
4.2 export FLYTE_UV_VERSION=0.5.2
4.3 export FLYTE_UV_VERSION=auto which return 0.6.12 returned by sub process result.
Setup process
Screenshots
Check all the applicable boxes
Related PRs
Docs link