Error when pointing UV_PROJECT_ENVIRONMENT to /usr/local/ on latest UV version 0.4.13

[rosssgill]

Hi there,

I've been previously using the docker image ghcr.io/astral-sh/uv:0.4.12-python3.11-bookworm-slim and successfully setting UV_PROJECT_ENVIRONMENT="/usr/local/" to point to the container's system python environment, similar to how @zanieb has done here: #6834 (comment). I noticed however that with the latest UV version 0.4.13, for example, using ghcr.io/astral-sh/uv:python3.11-bookworm-slim image, this is no longer possible and during the container build I get the following error:

[svc dev 6/8] RUN --mount=type=cache,target=/root/.cache/uv     --mount=type=bind,source=uv.lock,target=uv.lock     --mount=type=bind,source=pyproject.toml,target=pyproject.toml     --mount=type=bind,source=setup.py,target=setup.py     uv sync --frozen --no-install-project:
0.422 error: Project virtual environment directory `/usr/local/` cannot be used because it is not a virtual environment and is non-empty

I believe it may be related to this pull request #7527?

[zanieb]

Ah sorry that's an oversight from the protections we added in #7522.

l'll fix this right away.

[zanieb]

I have a fix up in #7585

I haven't tested it yet though — if want to make sure it works for you that'd be helpful. I'll be adding test coverage for this functionality before merging.

[zanieb]

This will be fixed in the next release (sometime today)

New integration test in #7591