devcontainer nos honoring dev.containers.dockerComposePath

[jjcasmar]

• VSCode Version: 1.91.1

• Local OS Version: Linux

• Remote OS Version: Linux

• Remote Extension/Connection Type: Containers

• Logs:

Start: Run: /usr/bin/podman compose --project-name mandos_devcontainer -f /home/jjcasmar/projects/Mandos/.devcontainer/docker-compose.yml -f /tmp/devcontainercli-jjcasmar/docker-compose/docker-compose.devcontainer.containerFeatures-1721642121005-2d9811f9-795d-43f1-b4ac-dca6b518ebae.yml up -d
>>>> Executing external compose provider "/usr/bin/docker-compose". Please refer to the documentation for details. <<<<

WARN[0000] /home/jjcasmar/projects/Mandos/.devcontainer/docker-compose.yml: `version` is obsolete 
WARN[0000] /tmp/devcontainercli-jjcasmar/docker-compose/docker-compose.devcontainer.containerFeatures-1721642121005-2d9811f9-795d-43f1-b4ac-dca6b518ebae.yml: `version` is obsolete 
[+] Running 0/1
 ⠸ Container mandos-dev  Creating                                          0.3s 
Error response from daemon: container create: creating container storage: the container name "mandos-dev" is already in use by b67c8e10d523964bd2d626efa48815a6cc367a30c6eda239106a3d5bbbc12bc0. You have to remove that container to be able to reuse that name: that name is already in use
Error: executing /usr/bin/docker-compose --project-name mandos_devcontainer -f /home/jjcasmar/projects/Mandos/.devcontainer/docker-compose.yml -f /tmp/devcontainercli-jjcasmar/docker-compose/docker-compose.devcontainer.containerFeatures-1721642121005-2d9811f9-795d-43f1-b4ac-dca6b518ebae.yml up -d: exit status 1

Steps to Reproduce:

1. Setup dev.containers.dockerComposePath= "podman-compose"
2. Try to run start a devcontainer. Will try to use docker-compose

When I set the dockerComposePath to podman-compose, devcontainer still tries to use docker-compose.

[chrmarti]

The shows podman compose calling docker-compose. I guess you have to configure podman compose to either error out (in which case the Dev Container CLI will use the configured dev.containers.dockerComposePath) or to call podman-compose.

[jjcasmar]

Is there any way to specify in vscode how podman compose called? Maybe I can add an envvar before calling it

[chrmarti]

You could start VS Code with an env variable set. Or: Add it to your local .bashrc (or similar file for your shell).

[jjcasmar]

Starting vscode witht the envar set is not an option. VSCode is connected to a remote session via ssh, and is in that ssh session where I want to start a devcontainer.

Setting PODMAN_COMPOSE_PROVIDER=podman-compose in zshrc (in the ssh remote server) is not working. I guess the file is not read when the session is open

[chrmarti]

Please append the Dev Containers log from when this happens. (F1 > Dev Containers: Show Container Log)

It should read env variables from your default shell.

[vs-code-engineering]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!