fix tgi-entrypoint wrapper in docker file: exec instead of spawning a child process #2663
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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