Skip to content
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

Questions about using docker images #73

Closed
boss-create opened this issue Jul 6, 2024 · 4 comments
Closed

Questions about using docker images #73

boss-create opened this issue Jul 6, 2024 · 4 comments

Comments

@boss-create
Copy link

In WSL, When installing using the recommended docker image:
docker pull runzhongwang/thinkmatch:torch1.6.0-cuda10.1-cudnn7-pyg1.6.3-pygmtools0.5.1

torch.cuda is unavailable and there are problems with symbolic links:
image

I also tried other different versions, and the above problems still occurred

@rogerwwww
Copy link
Member

It seems to be an issue when putting WSL + Nvidia driver + docker together. Can you confirm: can you run CUDA with torch outside docker?
To my best (but vague) knowledge of WSL, you may need WSL2 to have the Nvidia driver working properly.

@boss-create
Copy link
Author

It seems to be an issue when putting WSL + Nvidia driver + docker together. Can you confirm: can you run CUDA with torch outside docker? To my best (but vague) knowledge of WSL, you may need WSL2 to have the Nvidia driver working properly.

Thank you for your reply. The WSL I mentioned above is WSL2, and I have also confirmed that CUDA can be used normally in WSL2-Ubuntu22.04 without using docker.
I have used other docker environments in WSL2 before and did not encounter similar problems. At the same time, I also tried WSL2-Ubuntu20.04 to re-pull different versions of the docker images and the same problem occurred...

@rogerwwww
Copy link
Member

Would you mind checking microsoft/WSL#5663

And some StackExchange guys said the error is harmless https://superuser.com/questions/1707681/wsl-libcuda-is-not-a-symbolic-link

@rogerwwww
Copy link
Member

I am closing this issue because it is no longer active. Please feel free to re-open it if the issue still exists!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants