Skip to content

fix tgi-entrypoint wrapper in docker file: exec instead of spawning a child process #2663

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

Merged
merged 1 commit into from
Oct 17, 2024

Conversation

oOraph
Copy link
Collaborator

@oOraph oOraph commented Oct 17, 2024

reason: we added a docker wrapper script a while ago to fix missing .so issues encountered when spawning tgi in some cloud providers that add shared libs, related to cuda for example, but do not refresh the ld cache in container hooks. tgi was spawned as a child process instead of replacing the parent one (the process bound to the script iself). Thus, the wrapper script was receiving all the signals and we forgot to add proper handlers to forward them to the child. The parent/child mechanism is overkill in this case and we can just replace the wrapper by tgi once the cache is refreshed

reason: otherwise parent will receive the signals when we'd like tgi to receive them
keeping the parent/child is not necessary and would require the parent to handle signals to forward them properly to the child

Signed-off-by: Raphael Glon <[email protected]>
Copy link
Collaborator

@Narsil Narsil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Narsil Narsil merged commit 1b97e08 into huggingface:main Oct 17, 2024
1 check passed
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.

2 participants