Skip to content

Fix: initialize writable pip cache directory #277

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rapids-bot merged 1 commit into from
Sep 9, 2026
Merged

Fix: initialize writable pip cache directory #277

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions tools/rapids-init-pip
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,3 +21,10 @@
PIP_CONSTRAINT="${PIP_CONSTRAINT:-$(mktemp -d)/constraints.txt}"
touch "${PIP_CONSTRAINT}"
export PIP_CONSTRAINT

# GitHub mounts /github/home from the host in job containers, which can make
# pip's default cache directory unavailable to the container user. Keep the
# cache in the writable workspace unless a caller supplies its own location.
PIP_CACHE_DIR="${PIP_CACHE_DIR:-${GITHUB_WORKSPACE:-${PWD}}/.cache/pip}"
mkdir -p "${PIP_CACHE_DIR}"
export PIP_CACHE_DIR
Loading