Documentation for getting started with Warehouse Development shows the issue with WSL, but fails to mention issue limited to WSL1

[yatharth9]

Warehouse: getting started WSL quirks This link contains a tutorial for mitigating quirks in WSL and Windows, however, it is only applicable to WSL1, and for those who read the getting started guide, they have installed Docker for Linux also, which leads to the Windows version of Docker desktop to not respond.

Hence a change to the getting started documentation is needed, that clearly points out the different methods for WSL1 and WSL2 users.
Even Nick Janetakis has created a new tutorial for those using WSL2.

[cofiem]

Related to WSL2, an issue that is apparently new to WSL2 and not present in WSL1, is that File changes made by Windows apps on Windows filesystem don't trigger notifications for Linux apps.

This means that it is necessary to manually run webpack build for each change, as webpack --watch is never triggered from file changes. For example:

docker compose -f docker-compose.yml exec -it static npm run build -- --mode development

Unfortunately, running the npm run watch command on the Windows host fails due to missing files, although it does trigger on file changes.

A workaround is to use the WSL2 filesystem \\wsl$\, which does support notifying file changes. This has the downside that upgrading or changing the WSL2 linux distro (for example, sometimes when updating Docker for Windows) can mean that the files are lost.