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

• 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