-
Notifications
You must be signed in to change notification settings - Fork 648
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.
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
Issue with uv@0.2.7
in Dockerfile + venv
#4072
Comments
uv@0.2.7
in Dockerfile + venv
FWIW, you can also use |
Can you share any more on what is failing? |
Modifying the Dockerfile a bit, I eventually get:
Does that look familiar? |
Sorry for not posting that in the original issue. Yes, that's the issue I ran into using 0.2.7. |
Okay, thanks. |
Thanks! We'll have a fix out shortly. |
…nvironment (#4073) Closes #4072 This was an accidental change in #4029 in which I had updated the pull request to support virtual environments as requested in review and forgot to revert it. Separately, we shouldn't fail if `VIRTUAL_ENV` points to an empty directory and `SystemPython::Allowed` is used, will address that separately.
That was fast! Thank you. |
The release should be out now. Let us know if you run into any more problems :) |
I think I've encountered an issue related to (I believe) virtualenv detection when using uv in a dockerfile. Specifically, I noticed that my company's CI started failing on all images that rely on uv.
For reference, here is the dockerfile:
This started failing universally this morning.
I hopped in to a partial image (before this line that activates the venv
RUN /root/.cargo/bin/uv venv /opt/venv
), and found that it was running uv@0.2.7.This image works without issue when I replace
https://astral.sh/uv/install.sh
withhttps://github.com/astral-sh/uv/releases/download/0.2.6/uv-installer.sh
.I haven't had time to further debug, but just wanted to raise this issue in case others are trying to debug.
Edit: it seems to fail at this step on 0.2.7:
The text was updated successfully, but these errors were encountered: