search

microsoft / vscode-remote-release

Visual Studio Code Remote Development: Open any folder in WSL, in a Docker container, or on a remote machine using SSH and take advantage of VS Code's full feature set.
https://aka.ms/vscode-remote
Other
3.64k stars 285 forks source link

Development Containers don't work with Compose V2 #9389

Open UninspiredNickname opened 9 months ago

UninspiredNickname commented 9 months ago

Development Containers don't work with Compose V2. Standalone compose (V1) has reached EOL on July 2023 (https://docs.docker.com/compose/migrate/).

Logs:

...
[2024-01-15T14:10:46.904Z] Start: Run in Host: docker compose version --short
[2024-01-15T14:10:46.939Z] Host server: Error: spawn docker compose EACCES
    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)
[2024-01-15T14:10:46.940Z] Stop (36 ms): Run in Host: docker compose version --short
[2024-01-15T14:10:46.941Z] Host server: (node:6650) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 1)
(Use `node --trace-warnings ...` to show where the warning was created)

Steps to Reproduce:

  1. Everything works with docker-compose (standalone version, aka. V1)
  2. Change compose command via settings.json: "dev.containers.dockerComposePath": "docker compose"
  3. Installation errors out (see attached log)
chrmarti commented 8 months ago

You currently need to uninstall docker-compose or make it forward to docker compose (Docker Desktop for Windows / Mac has a setting for this).

The Dev Containers setting you are using does not support arguments.