-
Notifications
You must be signed in to change notification settings - Fork 704
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
Build error - command not found #5
Comments
can we get a little more context on this? you cloned the project in workbench and the build failed? or did you try and build things outside of workbench? |
I did as this part of the tutorial instructed.
I cloned it using the clone project button here after I created my own fork: The build starts but this is as far as it gets:
I went as far as firing up that container manually with: apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y libgl1
libglib2.0-0
git
jq that also fails. You get: ...
Setting up libgl1-mesa-dri:amd64 (23.2.1-1ubuntu3.1~22.04.2) ...
Setting up libglx-mesa0:amd64 (23.2.1-1ubuntu3.1~22.04.2) ...
Setting up libglx0:amd64 (1.4.0-1) ...
Setting up libgl1:amd64 (1.4.0-1) ...
Processing triggers for libc-bin (2.35-0ubuntu3.4) ...
bash: libglib2.0-0: command not found
bash: git: command not found
bash: jq: command not found It looks ilke these are getting pulled out of the file
to this:
and the build has progressed past step 22. I'm guessing the odd spacing is the source of the bug.
No - I did everything inside the Nvidia AI Workbench UI. No command line. |
It now seems to have an unrelated failure though. Full build log attached. I choose podman when prompted to choose during install because that's what most of my customers are running with K8s. A naive glance at the error makes me think the installer assumes
|
- Fixes NVIDIA#5 - This causes apt-get to fail the install because git, jq, etc are interpreted as commands rather than arguments to apt-get Signed-off-by: Grant Curell <[email protected]>
If you're good with the PR I'll move this to a separate issue. I can take a look at it on Monday. I didn't spend time looking to see if there are other dependencies assuming everything each be on its own line. |
When I told Workbench to clone the project for me it pulled everything with CRLF which caused the build to choke. I removed all the carriage returns recursively with:
Not sure if this is necessarily a problem with this project, but if you leave any of them either the build fails or the chat app itself fails. |
I have just started looking at this, but if this is meant to be an out of the box demo sort of deal, it looks like the build is broken. I just did a fresh install, let workbench deploy podman for me, and forked this repo. Below are the results.
System Info
Not that it really much matters since the build appears to be failing looking for some packages that don't exist in a container, but the host system is:
The text was updated successfully, but these errors were encountered: