Support local projects inside WSL with Docker provider

[pingu8007]

Is your feature request related to a problem?

To work with existing local projects inside WSL with Docker.
More exactly, to work with following setup:

• Windows host with WSL2 enabled
• Docker engine based on WSL, and Docker binary and endpoint are exposed to WSL distros
• Local projects are located inside one or more WSL distros
• IDE is installed on host

Which solution do you suggest?

If specified local path points to inside of WSL, detect the existence of Docker endpoint and rebuild path to local form.

Which alternative solutions exist?

Install Devpod inside WSL and config multi-hop SSH might work. Never tried.

Additional context

Most Docker solutions for Windows use WSL as their backend.
It's already known that accessing files on Windows from WSL has very poor performance, and VScode recommends cloning projects directly into WSL if possible.

You may also consider refactoring the file picker to natively support projects located on any remote side. It would be useful if the code is not allowed to leave the remote environment and is too large to clone every time.

[patrick-mota]

I came with the exact same feature request because, for me, working with Windows paths is very slow.

However, I think the feature you asked for is missing the SSH resolver too. When I SSH from Windows, it works, but not from WSL2. So, I guess if they implement WSL2 support, they will need to address that as well.

[zuka1337]

Any news on this one ?

[pascalbreuninger]

Hey @pingu8007, thanks for opening the issue. The windows path issue has been a long standing issue we intend to tackle it soon-ish.

Until then the workaround is to install VSCode and DevPod CLI in WSL manually, starting workspace from within WSL instead of from the windows host