-
Notifications
You must be signed in to change notification settings - Fork 20
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
Question: How to get started? #451
Comments
The RAPIDS libraries are built on top of NVIDIA CUDA, which doesn't run on MacOS. We use Linux-specific features, so we don't build packages for the Windows CUDA toolkit. However, we do support running RAPIDS in the Windows subsystem for Linux (WSL2). If you can run under WSL (or on Linux) with NVIDIA driver 510.47.03 or newer (which is the one that aligns with CTK 11.6.2), you can use the libraries in either of these two ways:
You can also use Linux or WSL to contribute to the libraries themselves, and the easiest way to do that is to develop in our dev containers. |
That's unexpected. What version of npm are you using? It must be installing the packages out of order. Try this: # Remove node_modules in case it's in a broken state
rm -rf node_modules
export RAPIDSAI_CUDA_VERSION=11
npm install @rapidsai/core
npm install @rapidsai/cudf In the meantime, I'll look into fixing our |
It seems something changed with npm recently. We'll need to skip running package scripts when we install Try with the export RAPIDSAI_CUDA_VERSION=11
npm i --ignore-scripts @rapidsai/core
npm i @rapidsai/cudf |
|
Thanks trxcllnt. After installing both with |
Oh yes, we build with the Ubuntu20.04 toolchain. node 18 has dropped Ubuntu18.04, so have too. As for the earlier error, that's what I'd expect to see if the libraries aren't actually downloaded. The The native modules are huge and we can't upload them to npm. The npm packages are just shell packages with the JS source code. At the moment I'm not sure what changed about npm to break this, but I'd suggest using yarn if you can. |
Do you have the CUDA driver installed in WSL? |
Actually, it seems |
I have the latest game ready driver installed for Windows 10, with the GPU being an RTX 3090. Looking at this page, I assume that's all that's needed?
|
Sounds like that'll give you the CUDA driver ( You shouldn't need the entire CUDA toolkit since we statically link as much as we can. I think all you need is the libnvrtc runtime library, which you can install this way: # https://developer.nvidia.com/cuda-downloads?target_os=Linux&target_arch=x86_64&Distribution=WSL-Ubuntu&target_version=2.0&target_type=deb_network
wget https://developer.download.nvidia.com/compute/cuda/repos/wsl-ubuntu/x86_64/cuda-keyring_1.0-1_all.deb
sudo dpkg -i cuda-keyring_1.0-1_all.deb
sudo apt-get update
# This assumes your driver aligns with the CUDA 12.0 release
# Change this version to match your driver if necessary.
sudo apt-get -y install cuda-nvrtc-12-0 |
Good news! Updating to CMake The bad news is I had to fix CMake to get it to link, so we'll have to wait till I think you're the first person to try using |
Hello,
I'm looking for some advice on this project.
Looking through the readme, I'm quite confused as to how to get up and running with this.
Do I need to run the docker images in order to run node code on my GPU?
Or do I just pull in the npm packages and code as normal? (Just tried that, and it fails as it's requiring Linux...) Does this mean I cannot run this on Windows/OSX ?
The text was updated successfully, but these errors were encountered: