Optimize Dockerfile with UV for faster dependency installation#92
Open
Optimize Dockerfile with UV for faster dependency installation#92
Conversation
Contributor
|
@rachfop I'm interested in this PR. Could you resolve the conflicting files when you have time? |
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
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.
Description
This PR introduces UV (https://github.com/astral-sh/uv) as a replacement for pip in the Dockerfile.
UV is a fast, reliable Python package installer and resolver, written in Rust. This change aims to significantly speed up the Docker build process, especially in CI/CD pipelines.
Changes
Benefits
Example of improvements
Basic pip installation:
RUN pip install --no-cache-dir -r requirements.txtWith UV:
RUN /root/.cargo/bin/uv pip install --system --no-cache -r requirements.txtTesting
Notes
--systemflag is used with UV to ensure system-wide installation, mimicking pip's default behavior in Docker.Future Considerations
I welcome any feedback or suggestions for improvement on this change.