Use uv sync --locked in Dockerfile#963
Merged
qin-ctx merged 1 commit intovolcengine:mainfrom Mar 25, 2026
Merged
Conversation
…resolution Without --locked, uv sync will silently re-resolve dependencies if pyproject.toml has drifted from the lockfile. This could pull in unexpected package versions during Docker builds. The --locked flag ensures the build fails fast if the lockfile is stale, matching uv's recommended practice for production builds (https://docs.astral.sh/uv/guides/integration/docker/).
qin-ctx
approved these changes
Mar 25, 2026
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
2 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.
Summary
--lockedflag touv syncin the Dockerfile build stage, following uv's recommended Docker practiceWhy
Without
--locked,uv syncwill silently re-resolve dependencies ifpyproject.tomlhas drifted fromuv.lock. In a Docker build this means a stale lockfile could cause unexpected package versions to be installed — a supply chain risk highlighted by the recent litellm incident.With
--locked, the build fails fast if the lockfile is inconsistent withpyproject.toml, ensuring Docker images are always built from the committed lockfile.Change