You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can probably use uv run --no-dev python -S -m uvicorn ...
It looks like there's an editable package or something writing the .pth? You could try not using an editable install or using a different build backend?
.pth files are generally used to power editable dependencies, e.g., uv pip install --editable ./foo. Why is site to writing this file in the first place?
Is fair to suggest creating a FAQ question for how to run uv on a read-only volume? I've also figured out I need to suppress or redirect .cache.
I'm not sure yet. I think I need to understand more about what's going on. This isn't really a uv-specific problem.
My
Dockerfile
implements aFastAPI
web server, as follows:The
/app
volume is read-only for safety reasons. At startup, python importssite
, whose documentation sayssite
attempts to write to this path, and fails because the volume is read-only:/app/.venv/lib/python3.11/site-packages/_myapp_back_end.pth
How do I get
uv
to be aware of running code on read-only volumes? Canuv
suppress this by somehow calling python with the-S
parameter?The text was updated successfully, but these errors were encountered: