5 ms·

Worth noting there are many different ways to get CUDA with WSL2 working. If you follow the MS docs, they do not mention anything about install CUDA on the Lin

Worth noting there are many different ways to get CUDA with WSL2 working. If you follow the MS docs, they do not mention anything about install CUDA on the Linux VM, you do not get a functional setup to start using CUDA and if you follow Nvidia's documentation, they push you down the docker container route. I personally prefer to setup Tensorflow using Anaconda rather than pip. A slight correct on the OP, the special driver NVIDIA mentions is for CUDA only (no display driver included), Nvidia does not "support" installing of their full display driver in WSL2 so YMMV in terms of reliability and performance. I personally gave up on WSL2, not because of WSL2, but because it is so hard to use remotely (I do not have frequent local access to my GPU workstation). I tried various instructions and WSL2 itself was fine when used locally (via remote desktop), but networking scripts I found were unreliable, or if I used Windows openssh server it kept crashing and bash.exe is too limited to be useful, just not worth the hassle and effort when I can install Linux native.

vl 5y ago
I used WSL2 with CUDA from linux for awhile, but forced update to Windows 11 (which broke everything) was a last straw for me. I went back to dual boot configuration with Ubuntu 20.04 LTS, and it saves so much time on fiddling with wsl, I highly recommend it.
- peatmonster 5y ago
  Getting a working Windows 10 install without it being liable to break itself is such an involved process..
  - supernovae 5y ago
    i never have any problems.
  - vijaybritto 5y ago
    Absolutely never had a single blue screen or random crash. Maybe its because its a laptop and not a hand built rig. Whats your's?
- bshipp 5y ago
  I also attempted a move to Win11 for CUDA before reinstalling Win10. I keep WSL because having a resident Ubuntu environment to install and run various scripts and bash commands/programs is really handy and has little overhead.
zeusk 5y ago
Just curious, why not RDP into Windows and use whatever you'd use locally to interact with WSL2?
password4321 5y ago
I recommend Bitvise SSH Server for Windows, which I've used for 10 years. It's free for personal use (also a free trial). As an aside: it supports blocking by client identifier, which completely shut down bot connections (and probably will until OpenSSH does the same).

vl 5y ago

I used WSL2 with CUDA from linux for awhile, but forced update to Windows 11 (which broke everything) was a last straw for me. I went back to dual boot configuration with Ubuntu 20.04 LTS, and it saves so much time on fiddling with wsl, I highly recommend it.

peatmonster 5y ago
Getting a working Windows 10 install without it being liable to break itself is such an involved process..
- supernovae 5y ago
  i never have any problems.
- vijaybritto 5y ago
  Absolutely never had a single blue screen or random crash. Maybe its because its a laptop and not a hand built rig. Whats your's?
bshipp 5y ago
I also attempted a move to Win11 for CUDA before reinstalling Win10. I keep WSL because having a resident Ubuntu environment to install and run various scripts and bash commands/programs is really handy and has little overhead.

zeusk 5y ago

Just curious, why not RDP into Windows and use whatever you'd use locally to interact with WSL2?

password4321 5y ago

I recommend Bitvise SSH Server for Windows, which I've used for 10 years. It's free for personal use (also a free trial). As an aside: it supports blocking by client identifier, which completely shut down bot connections (and probably will until OpenSSH does the same).