Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Setuv UV_PYTHON_INSTALL_DIR explicitly#3197

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
sebastianliebscher wants to merge1 commit intohuggingface:main
base:main
Choose a base branch
Loading
fromsebastianliebscher:allow_non_root_container

Conversation

sebastianliebscher
Copy link

@sebastianliebschersebastianliebscher commentedApr 27, 2025
edited
Loading

What does this PR do?

In recent commits,uv was introduced. When installing Python viauv python install itdefaults to~/.local/share/uv/python. Since the user context in the base stage of the Dockerfile is root, the default path resolves to/root/.local/share/uv/python. Unfortunately, this directory is not accessible to non-root users in unprivileged containers, e.g.

docker run --rm --entrypoint bash -it --user 1000 ghcr.io/huggingface/text-generation-inference:3.2.3 -c"ls /root/.local/share/uv"ls: cannot access'/root/.local/share/uv': Permission denied

This PR fixes this by explicitly setting theUV_PYTHON_INSTALL_DIR variable to/usr/share/uv which is accessible for non-root users.

Fixes#3082
Fixes#3225

Before submitting

  • This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
  • Did you read thecontributor guideline,
    Pull Request section?
  • Was this discussed/approved via a Github issue or theforum? Please add a link
    to it if that's the case.
  • Did you make sure to update the documentation with your changes? Here are the
    documentation guidelines, and
    here are tips on formatting docstrings.
  • Did you write any new necessary tests?

Who can review?

Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

@Narsil

julseil and mwm5945 reacted with thumbs up emoji
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Launching a container with an unprivileged user Running container rootless does not work anymore
1 participant
@sebastianliebscher

[8]ページ先頭

©2009-2025 Movatter.jp