This is a workaround to the problem I face most of the time when I run cuda powered apps on windows with wsl-2 beta.
I guess the reason is that for a beta version Microsoft is offering their own version of nvidia driver with built-in cuda library, and that's why maybe some of the shared libraries are being duplicated with host ones and creating incompatibility issue.
Also who are new to this topic, Windows finally introduced WSL-2 integration with Cuda and linux users can somehow feel potential use of video-card in their wsl based linux environments.
Check it out here
#ldconfig #libcuda #wsl #wsl2 #windows #cuda #so
I guess the reason is that for a beta version Microsoft is offering their own version of nvidia driver with built-in cuda library, and that's why maybe some of the shared libraries are being duplicated with host ones and creating incompatibility issue.
Also who are new to this topic, Windows finally introduced WSL-2 integration with Cuda and linux users can somehow feel potential use of video-card in their wsl based linux environments.
Check it out here
#ldconfig #libcuda #wsl #wsl2 #windows #cuda #so
GitHub
libcuda.so.1 is not a symbolic link · Issue #5548 · microsoft/WSL
This is cross-post of Ubuntu bug 1886532 which is pending investigation. On Windows 10 build 20161 WSL2 running sudo apt upgrade results in warning: "libcuda.so.1 is not a symbolic link" ...