chore: Use shared volume for devcontainer uv cache #304
Conversation
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
Instead of mounting the user's local cache. For the first use this will be slower (if the user has previously used uv) but using a separate volume means links within the cache referring to devcontainer locations will not interfere with uv being run from outside the container. Using a named volume means devcontainers for multiple projects can share the same cache.
tpoliaw
force-pushed
the
volume_cache
branch
2 times, most recently
from
1509ae6 to
89f799f
Compare
tpoliaw
changed the title
coretl
added a commit
that referenced
this pull request
Oct 28, 2025
Supercedes #304 and #305 by adding a global volume that contains: - pre-commit cache - uv cache - uv managed python cache - the venvs for all the projects This allows us to use hardlink mode which makes it even faster, and avoid the issue of anonymous volumes in devcontainers being left dangling. Added docs to say that there is now a global venv for the container, which is different for how it would look without any environment variables set
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.
Instead of mounting the user's local cache. For the first use this will
be slower (if the user has previously used uv) but using a separate
volume means links within the cache referring to devcontainer locations
will not interfere with uv being run from outside the container.
Using a named volume means devcontainers for multiple projects can share
the same cache.