Skip to content

entrypoint_user_scripts.sh: ensure pip runs in venv#256

Closed
edgar-vincent wants to merge 1 commit intopSpitzner:release/2.0.0from
edgar-vincent:fixerequirementstxt
Closed

entrypoint_user_scripts.sh: ensure pip runs in venv#256
edgar-vincent wants to merge 1 commit intopSpitzner:release/2.0.0from
edgar-vincent:fixerequirementstxt

Conversation

@edgar-vincent
Copy link

Since 67afd94, beets runs in a venv. However, entrypoint_user_scripts.sh installs user-defined requirements in requirements.txt system-wide via pip, which makes them inaccessible to beets.

This PR makes sure the requirements are installed in the venv. It also makes sure pip is available in the pip in order to avoid silent failures.

@semohr
Copy link
Collaborator

semohr commented Jan 7, 2026

Thanks for the PR!

As far as I know we use should use the python executable that is bundled with with the base image (even when using uv). If this is not working as expected we might have a bug in our Dockerfile. I would rather try to fix this properly in the Dockerfile than have a solution to check for virtual environment that should not exist in the first place.

We had this before but it seems to be missing in the 2.0.0 version.

# avoid creating a venv with uv, use system python
ENV UV_PROJECT_ENVIRONMENT="/usr/local/"

@edgar-vincent
Copy link
Author

#257 fixes it here. Beautiful, thanks!

@pSpitzner
Copy link
Owner

pSpitzner commented Jan 7, 2026

#257 fixes it here. Beautiful, thanks!

lol. that was quick! Awesome, thanks :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants