Remote development cannot abide multiple remote containers defined in compose files with the same service name running simultaneously

[extradosages]

I have two different remote development environments. Each environment spins up a remote development container according to a docker-compose.yaml referenced in the devcontainer.json declaration. Both compose files specify the deployment of the container under a service called vscode.

Spinning up either on their own works fine. However, if one is running, vscode will fail to spin up the second. This is because instantiation attempts to find running instances of an environment with the following command:

[2021-10-13T21:42:29.404Z] Start: Run: docker ps -q -a --filter label=com.docker.compose.project=vscode --filter label=com.docker.compose.service=vscode
[2021-10-13T21:42:29.437Z] Stop (33 ms): Run: docker ps -q -a --filter label=com.docker.compose.project=vscode --filter label=com.docker.compose.service=vscode

which obviously can't tell the difference between the two containers.

The totality of the documentation that I have found on this subject is here: https://code.visualstudio.com/remote/advancedcontainers/connect-multiple-containers.

How can I add additional metadata to each of these declarations that will be used by remote containers to distinguish between the two? If I can't I would suggest that this is a bug-- that all projects shouldn't share the same implicit namespace for their services.

Environment details:

Version: 1.62.0-insider
Commit: 284e0db6c4cac1e557a43cd6691babdaafc2e1a9
Date: 2021-10-12T05:44:48.500Z
Electron: 13.5.1
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Linux x64 5.13.19-2-MANJARO

[extradosages]

I have to wonder if this is the same issue as #5697.

[chrmarti]

Docker Compose derives the project name from the folder's basename which seems to be vscode in both your remote environments. Try renaming one of the folders or set COMPOSE_PROJECT_NAME with an .env file in one of the workspace folders. Does that help?

[extradosages]

It does. Excellent help, seems like this is more of a docker-compose thing than a vscode thing.
For those who are interested, here's a link to the relevant discussion in compose world: docker/compose#745 and in the compose spec world: compose-spec/compose-spec#206.

Thanks, @chrmarti .