-
Notifications
You must be signed in to change notification settings - Fork 2
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
Issues under WSL2 #1
Comments
YOu may be able to do a PR with some of the modifications found here to make it work? I don't have a WSL machine to test these on (just Linux), so let me know if they work and contribute back if you can :) |
After using |
@qingfengfenga that's great to know! Read through the closed issue you linked and it seems promising. I'll merge this into main. When it comes to building the image, I'll create a release candidate one in this repository, but feel free to build it for yourself locally or for your own GHCR registry. Please let me know if the pushed image or your own locally built one isn't working. Thank you for looking into this! 😄 |
Issues
Thank you very much for your work. I have attempted to run K3S and CUDA workloads under WSL2. Based on this issue and the files provided by your repository, I have conducted testing and I feel that it is almost successful.
The current issue is that the nvidia device plugin pod can execute nvidia smi, but the logs indicate that the graphics card cannot be recognized.
I suspect it may be due to the unavailability of NVCC. Do you have any ideas?
System:Win11 23H2
Runtime:Docker Desktop 4.28.0 (139021)
nvidia-device-plugin log
nvidia-device-plugin pod run nvidia-smi / nvcc
cuda-vector-add pod describe
The text was updated successfully, but these errors were encountered: