-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
error: make -C docker release_build : Command 'git submodule update --init --recursive' returned non-zero exit status 128 #2479
Comments
I follow this page, it works: https://www.dong-blog.fun/post/1863 By the way, I have an additional question. I noticed that the interface for accessing this Triton deployment is quite stiff. Is there a question-and-answer interface similar to OpenAI's available? When I access it this way, the model's responses seem to be completing my sentences rather than the usual question-and-answer format.
|
To fix the
|
@xddun Do you still have this issue? |
thanks |
System Info
env:
ubuntu22
RTX3090
Linux euler-MS-7D30 6.8.0-45-generic #45~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Sep 11 15:25:05 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
I wanted to build an image, but unexpectedly encountered an error. My process was as follows in 4steps:
git clone https://github.com/NVIDIA/TensorRT-LLM.git
cd TensorRT-LLM
git lfs pull
make -C docker release_build
error log:
Who can help?
Is it possible to provide a pre-configured image with the environment already set up? Compiling the image is really challenging!
Information
Tasks
examples
folder (such as GLUE/SQuAD, ...)Reproduction
env:
ubuntu22
RTX3090
Linux euler-MS-7D30 6.8.0-45-generic #45~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Sep 11 15:25:05 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
I wanted to build an image, but unexpectedly encountered an error. My process was as follows in 4steps:
git clone https://github.com/NVIDIA/TensorRT-LLM.git
cd TensorRT-LLM
git lfs pull
make -C docker release_build
error log:
Expected behavior
actual behavior
additional notes
The text was updated successfully, but these errors were encountered: