Cannot start a dev container when connected to WSL2 through VSCode Tunnels

[a-gn]

• VSCode Version: 1.85.0
• Local OS Version: macOS Sonoma 14.1.2 (23B92)
• Remote OS Version: Windows 11
• Remote Extension/Connection Type: Tunnel -> WSL2 -> (not working) Dev Containers

• Logs:

In the Dev Containers log:

[2680055 ms] Start: Run: wsl -d Ubuntu@tunnel+pc -e /bin/sh -c cd '/home/me/project/src' && /bin/sh
[2680057 ms] Start: Run in host: id -un

In the dev console:

  ERR Shell server failed: Error: spawn wsl ENOENT
	at ChildProcess._handle.onexit (node:internal/child_process:283:19)
	at onErrorNT (node:internal/child_process:476:16)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21): Error: Shell server failed: Error: spawn wsl ENOENT
	at ChildProcess._handle.onexit (node:internal/child_process:283:19)
	at onErrorNT (node:internal/child_process:476:16)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
	at d.h (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:141:140441)
	at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Steps to Reproduce:

1. Connect to a Windows computer through Tunnels.
2. Connect to WSL2 on that machine with the Remote - WSL extension.
3. Open a WSL2 folder that contains a .devcontainers configuration.
4. Run the "Reopen in Container" command.

I expect that VSCode start building a dev container using my configuration and open the same folder in the container. Instead, nothing happens, I get no feedback besides the logs I posted above.

Does this issue occur when you try this locally?: No Does this issue occur when you try this locally and all extensions are disabled?: No

[OneCyrus]

just had the same issue. can confirm that it doesn't work here either.

[nag92]

I have the same issue too

[thisismygitrepo]

same, W10, WSL(Ubuntu 20.04)

[nag92]

I was able to solve the problem by deleting all the config files in the .vscode directory. factorying resetting Docker, reinstalling Ubuntu and not having the "Execute in WSL": selected

[ArnoGW1]

Same issue in the same situation, but now I get this popup:

Command 'Dev Containers: Rebuild and Reopen in Container' resulted in an error

Shell server failed: Error: spawn wsl ENOENT at ChildProcess._handle.onexit (node:internal/child_process:286:19) at onErrorNT (node:internal/child_process:484:16) at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

[jgsqware]

same here

[lnguyen4]

Same issue in the same situation, but now I get this popup:

Command 'Dev Containers: Rebuild and Reopen in Container' resulted in an error

Shell server failed: Error: spawn wsl ENOENT at ChildProcess._handle.onexit (node:internal/child_process:286:19) at onErrorNT (node:internal/child_process:484:16) at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

I got the exact same error. I am using local a Linux machine and tried to remote-tunnel to a remote WSL2 win11 desktop.

[tungts1101]

Is there any progress on this feature?

[cjsj166]

I had the same problem with following action: ssh into windows from my local ubuntu, connect to wsl, try to attach docker container. Somehow it seems that vs code tries to run wsl on my local PC, which obviously doesn't work as my PC is ubuntu. I just ssh into windows and then attach to docker container right away without connecting to wsl. And then it worked. I guess using windows version docker could be a solution.

[CECapps]

Throwing another "me too" on the pile here, but I'm very confused about the classification of this problem.

@chrmarti This is not a feature request. This is a bug. Feature requests don't have error messages with stack traces. WSL and Dev containers working correctly is expressly advertised on the web page documenting the feature: https://code.visualstudio.com/docs/remote/tunnels#_can-i-use-other-remote-development-extensions-or-a-dev-container-while-im-tunneling