-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Don't hardcode TCNN_CUDA_ARCHITECTURES in Dockerfile #1317
Comments
I see this could cause issues. So, I tried to create a new docker image with tinycudnn supporting multiple CUDA architecures, however I cannot validate as I only have access to RTX3000 and RTX4000 cards. Could someone who had issues with using docker before test the new image and give feedback for This should support the following GPUs and corresponding CUDA architectures:
|
So, I got one confirmation that it is working now, looking for an additional one to be sure. As soon as I get this IÄll update the Dockerfile and description. |
@Zunhammer it is indeed working with 0.16 here on a 1660Ti. |
Thanks for fixing this so quickly @Zunhammer! |
My graphics is NVIDIA GeForce RTX 3090/PCIe/SSE2 / NVIDIA Corporation. And I am still having problems. sudo docker run -it --rm --gpus all dromni/nerfstudio:0.3.1 ==========
|
It's not able to detect your GPU, usually this is caused by an outdated nvidia driver (must be at least be compatible with CUDA 11.8) or misconfigured docker. Try to use a nvidia docker image and run nvidia-smi inside to see if your GPU is passed through correctly. |
GPU is passed through correctly CUDA Version 11.8.0 Container image Copyright (c) 2016-2022, NVIDIA CORPORATION & AFFILIATES. All rights reserved. This container image and its contents are governed by the NVIDIA Deep Learning Container License. A copy of this license is made available in this container at /NGC-DL-CONTAINER-LICENSE for your convenience. Fri Jun 9 09:49:46 2023 +-----------------------------------------------------------------------------+ |
This line:
nerfstudio/Dockerfile
Line 10 in 0e9e26d
Seems to be the cause of a few issues: #1056, #1297, #1168
A workaround was proposed by @dragonheat123: #1056 (comment)
Maybe somebody who knows more about Docker can help automate this?
cc @Zunhammer
The text was updated successfully, but these errors were encountered: