use compose commands with projects that have been started via api does not work

I have a vscode and a portainer container running in parallel on my host. Both can communicate via /var/run/docker.sock with the host

My stacks are deployed from portainer via api, which means that "docker compose ls" does not show a "CONFIG FILES" entry.

With this setup most of the "Docker Tools" run fine --- I can see the containers grouped by my portainer stacks.

But when I try to execute a command on the stack (==docker compose [command]), I get "Error: Unable to determine compose project info for container group 'cockpit'."

From my terminal, I can run these commands via "docker compose -p cockpit [command]".

I think that you should pass the -p parameter to the compose command, especially when there is no direct connection to a docker-compose.yml due to the fact that the stack has been deployed via api.

Best regards,
Jan

Start by tracing the Docker Tools handling for docker compose commands when docker compose ls has no CONFIG FILES entry. Reproduce the Portainer API deployment with the cockpit project and compare it with docker compose -p cockpit [command]. Done means compose commands work for that container group without a compose file path.