Use COMPOSE_PROJECT_NAME or -p with the `up` command

[mathroc]

Description

When a project already exists, I would like to be able to do COMPOSE_PROJECT_NAME=myproject docker compose up to update the stack when its config changed for example, or do --force-recreate some-service, etc.

It's useful when docker compose is wrapped by other tools adding their own config file to the docker compose project but in different folders (eg: devcontainer, devpod) since I can't just go to the folder where the docker-compose.yml is, I would have to also figure out where are all the other config files and specify them.

but this is information that's already known by docker compose:

❱ docker compose ls
NAME                STATUS              CONFIG FILES
iterou              running(3)          /home/mathieu/Projects/iterou/.devcontainer/docker-compose.yml,/tmp/devcontainer-zed/docker_compose_build.json,/tmp/devcontainer-zed/docker_compose_runtime.json

[ndeloof]

the CONFIG FILES details was introduced for Docker Desktop benefits but isn't actually enough so one could run up command to reconcile actual resource with compose config (we miss the actual environment used to run the original app). This is a legacy I'd like we remove from compose as this brings confusion.

[tanikush]

Hi @ndeloof, I'd like to work on this if it's still available. I'll investigate the current implementation and the discussion before proposing a solution.