Skip to content

Running container rootless does not work anymore #3082

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

Open
2 of 4 tasks
scriptator opened this issue Mar 7, 2025 · 3 comments · May be fixed by #3197
Open
2 of 4 tasks

Running container rootless does not work anymore #3082

scriptator opened this issue Mar 7, 2025 · 3 comments · May be fixed by #3197

Comments

@scriptator
Copy link

System Info

Any environment, as long as you the TGI container with user != 0.

Information

  • Docker
  • The CLI directly

Tasks

  • An officially supported command
  • My own modifications

Reproduction

Symptom

I cannot run the current TGI image with user different than root

docker run --platform linux/amd64 -it --user 1000 ghcr.io/huggingface/text-generation-inference:3.1.1

fails immediately with the following error message

unable to refresh ld cache, not a big deal in most cases
/usr/local/bin/text-generation-launcher: error while loading shared libraries: libpython3.11.so.1.0: cannot open shared object file: No such file or directory

Error analysis

  • The python library which cannot be found is installed in /root/.local/share/uv/python/cpython-3.11.11-linux-x86_64-gnu/lib/
  • The directory /root/ is not readable for non-root users.
  • I suspect that the problem has been introduced with Moving to uv instead of poetry. #2919 because release v3.0.1 still works.

Expected behavior

I expect to be able to run TGI with non-root users, e.g. on Kubernetes. This was possible previously.

@andresC98
Copy link

Hi, we currently have the same issue:

#3043 (comment)

@sebastianliebscher
Copy link

sebastianliebscher commented Apr 23, 2025

Same issue too with v3.2.3. Setting different env vars did not fix the issue. Building a custom docker image shouldn't be the solution as proposed in the linked issue . Any ideas?

@sebastianliebscher
Copy link

Also related: v3.1.1 introduced #2999

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 a pull request may close this issue.

3 participants