Attempting to run a devcontainer using an existing docker-compose.yml fails

[ThomasOwens]

• VSCode Version: 1.89.1

• Local OS Version: Windows 11 Pro 10.0.22621 Build 22621

• Remote OS Version:

• Remote Extension/Connection Type: Dev Container

• Logs:

[6186 ms] Start: Run: docker ps -q -a --filter label=com.docker.compose.project=testproject --filter label=com.docker.compose.service=web
[6294 ms] Start: Run: docker inspect --type container 61a40a4873be
[6385 ms] Start: Inspecting container
[6385 ms] Start: Run: docker inspect --type container 61a40a4873be5abc2747ba15a1a156d6d92d5688c2058c4e2f7431f5c3755605
[6478 ms] Start: Run in container: /bin/sh
[6485 ms] Start: Run in container: uname -m
[6570 ms] Shell server terminated (code: 1, signal: null)
[6570 ms] Error response from daemon: container 61a40a4873be5abc2747ba15a1a156d6d92d5688c2058c4e2f7431f5c3755605 is not running
[6571 ms] Start: Run in container:  (command -v getent >/dev/null 2>&1 && getent passwd 'root' || grep -E '^root|^[^:]*:[^:]*:root:' /etc/passwd || true)
[6571 ms] Stdin closed!
[6571 ms] Error: An error occurred setting up the container.
[6571 ms]     at utA (c:\Users\thoma\.vscode\extensions\ms-vscode-remote.remote-containers-0.362.0\dist\spec-node\devContainersSpecCLI.js:409:3888)
[6571 ms]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[6571 ms]     at async KtA (c:\Users\thoma\.vscode\extensions\ms-vscode-remote.remote-containers-0.362.0\dist\spec-node\devContainersSpecCLI.js:481:3865)
[6571 ms]     at async $C (c:\Users\thoma\.vscode\extensions\ms-vscode-remote.remote-containers-0.362.0\dist\spec-node\devContainersSpecCLI.js:481:4807)
[6571 ms]     at async hrA (c:\Users\thoma\.vscode\extensions\ms-vscode-remote.remote-containers-0.362.0\dist\spec-node\devContainersSpecCLI.js:661:13255)
[6571 ms]     at async lrA (c:\Users\thoma\.vscode\extensions\ms-vscode-remote.remote-containers-0.362.0\dist\spec-node\devContainersSpecCLI.js:661:12996)
[6580 ms] Exit code 1
[6583 ms] Command failed: C:\Program Files\Microsoft VS Code\Code.exe c:\Users\thoma\.vscode\extensions\ms-vscode-remote.remote-containers-0.362.0\dist\spec-node\devContainersSpecCLI.js up --user-data-folder c:\Users\thoma\AppData\Roaming\Code\User\globalStorage\ms-vscode-remote.remote-containers\data --container-session-data-folder /tmp/devcontainers-22e6f661-cbe0-4ebf-8657-f9f6dfa10a6b1715950748061 --workspace-folder c:\Users\thoma\Projects\TestProject --workspace-mount-consistency cached --id-label devcontainer.local_folder=c:\Users\thoma\Projects\TestProject --id-label devcontainer.config_file=c:\Users\thoma\Projects\TestProject\.devcontainer\devcontainer.json --log-level debug --log-format json --config c:\Users\thoma\Projects\TestProject\.devcontainer\devcontainer.json --default-user-env-probe loginInteractiveShell --mount type=volume,source=vscode,target=/vscode,external=true --mount type=bind,source=\\wsl.localhost\Ubuntu\mnt\wslg\runtime-dir\wayland-0,target=/tmp/vscode-wayland-91b5fcee-56ef-455b-b306-605b43ec7dae.sock --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root
[6583 ms] Exit code 1

Steps to Reproduce:

1. I created a Dockerfile and docker-compose file. When running these, independently, the container is built and runs as expected.
2. I used the VS Code functionality to add Dev Container configuration files to the workspace, using a pre-existing docker-compose.yml.
3. When I attempt to run and connect to the dev container, the above log is generated.

Does this issue occur when you try this locally?: Yes Does this issue occur when you try this locally and all extensions are disabled?: Unsure.