Be aware of the fact that WSL 1 and 2 can coexist. Running wsl -l -v from PowerShell should tell you which distribution is using which subsystem. You can change between the two.
If you're using WSL 2 and you put your Linux files on the Windows filesystem IO performance becomes spectacularly awful. If you keep your Linux files on the Linux filesystem it works rather well.
Docker should be installed on the Windows side with Docker Desktop and then associated with your Linux machines under Docker Desktop settings. This makes it available on both Windows and Linux. If you install it directly on Linux it only becomes available on that Linux installation and you get no interoperability.
Systemd tools will yell at you. I encountered issues when running systemctl. There are some fixes but I don't know if they work because I'm lazy so I worked around the issue instead.
I don't know if accessing the Linux files from Windows breaks them. I'm using VSCode remote extensions instead of mounting \\wsl$ and accessing it directly.
If you're using WSL 2 and you put your Linux files on the Windows filesystem IO performance becomes spectacularly awful. If you keep your Linux files on the Linux filesystem it works rather well.
Docker should be installed on the Windows side with Docker Desktop and then associated with your Linux machines under Docker Desktop settings. This makes it available on both Windows and Linux. If you install it directly on Linux it only becomes available on that Linux installation and you get no interoperability.
Systemd tools will yell at you. I encountered issues when running systemctl. There are some fixes but I don't know if they work because I'm lazy so I worked around the issue instead.
I don't know if accessing the Linux files from Windows breaks them. I'm using VSCode remote extensions instead of mounting \\wsl$ and accessing it directly.