Reference Documents

The following hyperlinks are in no particular order. I am collecting these links as I close the tabs out and are storing them here primarily as a guide for my friend. My intent or hope is that it helps reveal my own workflow during software development.

hyperlinks cache

1. WSL: systemd

2. Docker Docs: compose-file spec

3. Docker Docs: Dockerfile

4. Docker Compose Reference: GPU Support

5. vscode docs: Setup on Linux

6. DebianWiki: Visual Studio Code

7. DockerHub: Debian Images

8. Docker Hub: itaru2622/vscode

9. https://stackoverflow.com/questions/72356527/nvidia-smi-gives-an-error-inside-of-a-docker-container

10. https://stackoverflow.com/questions/69586539/why-does-nvidia-smi-show-same-cuda-version-and-driver-version-both-inside-and-ou

WSL2

TODO(JEFF): We must test some of the proposed fixes for resolving the performance issues involved with crossing the filesystem barriers between Linux and Windows kernels. I believe that the solution exists within these links below.

In short, the proposed solutions involve setting up [VSCode][] with the Remote Tunnel extension (Windows) that is then directed at an install of vscode on WSL2 already listening for inbound connections. Once filesystem access is established like so, one can setup additional extensions, such as the official Docker extension for [VScode][] for extra convenience (service control without terminal).

\\wsl2.localhost\Debian\     

1. how I fixed wsl2 filesystem performance issues

2. https://superuser.com/questions/1114341/windows-10-ubuntu-bash-shell-how-do-i-mount-other-windows-drives

3. wsl2-how-to-prepare-and-attach-virtual-drives

4. https://askubuntu.com/questions/1340815/moving-files-between-wsl-and-windows

5. why is wsl extremely slow when compared with native windows npm yarn processing

   • This page has benchmarks & metrics to back up the issue and solutions!

6. https://www.reddit.com/r/wsl2/comments/171793u/windows_wsl2_poor_file_system_performance/

7. https://news.ycombinator.com/item?id=33629826