recently dual system collapsed, so choose wsl2, save trouble in the future, the first is the installation method, here posted my reference to some posts and introduction:
win10 installation method of wsl2 and docker-ce:
https://blog.csdn.net/xianxi9883/article/details/107358445/
win10 on container virtualization:
https://blog.csdn.net/leenhem/article/details/105359112
http://www.xitongcheng.com/jiaocheng/win10_article_53803.html
introduces wsl2 installation driver and nvidia-docker method:
https://zhuanlan.zhihu.com/p/149517344
here are some of the problems I ran into:
is
curl https://get.docker.com | sh
speed is very slow, tried two days all can’t, finally changed a unicom network…
solved in minutes
followed by:
curl -s -L https://nvidia.github.io/nvidia-docker/gpgkey | sudo apt-key add -
prompt me GPG: no valid OpenPGP data found.
then I start from the browser open https://nvidia.github.io/nvidia-docker/gpgkey, download this file to the ubuntu folder p>
sudo apt-key add gpgkey
solution p>
and then
curl -s -L https://nvidia.github.io/nvidia-docker/$distribution/nvidia-docker.list | sudo tee /etc/apt/sources.list.d/nvidia-docker.list
because I couldn’t find nvidia-docker in the last update of the whole process, so I checked the nvidia-docker list and found nothing, so I opened the previous link separately, took the data and wrote it in by myself.
deb https://nvidia.github.io/libnvidia-container/stable/ubuntu16.04/$(ARCH) /
#deb https://nvidia.github.io/libnvidia-container/experimental/ubuntu16.04/$(ARCH) /
deb https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu16.04/$(ARCH) /
#deb https://nvidia.github.io/nvidia-container-runtime/experimental/ubuntu16.04/$(ARCH) /
deb https://nvidia.github.io/nvidia-docker/ubuntu16.04/$(ARCH) /
, that’s what it is. If you want to open it yourself, you can use
https://nvidia.github.io/nvidia-docker/$distribution/nvidia-docker.list, where $distribution changing its own system name p>
and finally, success.
Read More:
- The nvidia-smi has failed because it could’t communicate with the NVIDIA driver
- [Solved] NVIDIA-SMI has failed because it couldn‘t communicate with the NVIDIA driver.
- How to Fix NVIDIA-SMI has failed because it couldn‘t communicate with the NVIDIA driver.
- Error reporting using NVIDIA SMI
- Nvidia-smi has failed because it could’t communicate with the NVIDIA driver
- Configure Nvidia graphics card on ubuntu18.04 xrandr Failed to get size of gamma for output default
- Resolved failed call to cuinit: CUDA_ ERROR_ NO_ DEVICE
- nvidia-settings: ERROR: nvidia-settings could not find the registry key file
- Error response from daemon: Conflict: unable to delete 8598c91556dc (must be forced)
- NVIDIA NVML Driver/library version mismatch
- Failed to initialize nvml driver / library version mismatch due to automatic update of NVIDIA driver
- NVIDIA docker failed to start normally
- Use NVIDIA to solve NVIDIA’s
- NVIDIA-SMI has failed because it couldn’t communicate with the NVIDIA driver
- NVIDIA SMI caused by updating BIOS has failed because it could’t communicate with the NVIDIA
- RuntimeError: CUDA out of memory. Tried to allocate 600.00 MiB (GPU 0; 23.69 GiB total capacity)
- After the new video card rtx3060 arrives, configure tensorflow and run “TF. Test. Is”_ gpu_ The solution of “available ()” output false
- Solve the startup error “something Wen wrong” of NVIDIA geforce experience
- Problems in the construction of CUDA environment (GPU parallel programming)
- Solution to x service error when installing NVIDIA graphics driver under Ubuntu