Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support local projects inside WSL with Docker provider #1131

Open
pingu8007 opened this issue Jun 21, 2024 · 1 comment
Open

Support local projects inside WSL with Docker provider #1131

pingu8007 opened this issue Jun 21, 2024 · 1 comment

Comments

@pingu8007
Copy link

pingu8007 commented Jun 21, 2024

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
Copy link

patrick-mota commented Jun 21, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants