WSL2 support for SSH provider #1932
Description
Is your feature request related to a problem?
My project contains long filenames so using the local Docker provider is not even an option since DevPod clones the repo into the Windows filesystem. Also the Windows filesystem is slow and prolematic for Linux-centric projects. It would be much better to use WSL's file system.
As an alternative I tried to set up the SSH provider with a remote server. I already have access to this remote server via my WSL config, but in Windows I do not have access to it. Example:
PS C:\Users\elite> ssh -oStrictHostKeyChecking=no -oBatchMode=yes colin@****.****.****.io echo Devpod Test
colin@****.****.****.io: Permission denied (publickey,password).
PS C:\Users\elite> wsl ssh -oStrictHostKeyChecking=no -oBatchMode=yes colin@****.****.****.io echo Devpod Test
Devpod Test
I'm sure I could get SSH working in native Windows, but it would be nice to be able to specify the command line prefix for the "ssh" command so in my case I could use "wsl ssh" and use the environment I'm already using heavily.
Which solution do you suggest?
If WSL2 is detected as present allow WSL2 to provide the "ssh" command instead of Windows' native SSH.
Which alternative solutions exist?
Setting up native Windows SSH client (yuck) and ignoring/discarding WSL2's SSH client.
Additional context
Trying to migrate from my WSL2-centered development workflow to DevPod.