-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
Various fixes to get rules_cuda to work with Lambda-stack #74
Conversation
Just curious, in |
Ubuntu provides both versioned and unversioned copies so it works. |
I need to add a test stage for this before a merge. In the future, we might need a process to re-compose a canonical tree, and it will also be useful for #72 |
@lalaland Could you please rebase on main and unconmment
|
fc5134f
to
0f201d2
Compare
@cloudhan Rebased and enabled. Note that you will have to manually trigger the workflows. |
@cloudhan Can you try rerunning it? I think you forgot to include the nvidia toolkit in your build script. I just added it so it should work now. |
Hmm. It looks like ubuntu ships an incompatible gcc and nvidia toolkit in their default packages? That's really quite lame. I added some code to the build script to try to downgrade the compiler. |
Sorry for the bother, but could someone try triggering the workflow again? I think I finally have the solution. |
Looks like everything passes now! This should be good to merge. |
The rules for this repository do not currently work with the following commonly used CUDA configuration: https://lambdalabs.com/lambda-stack-deep-learning-software
The reason is because the Lambda deep stack installs CUDA in /usr/bin, which breaks a couple of assumptions with this software.
In particular:
This fixes those two issues.