Describe the bug

Current compose uses explicit container names and network names which makes it impossible to start two stacks side by side.

Steps to reproduce

Start one stack. Create a worktree to start a different stack.

$ git worktree list
~/src/github.com/ChristianKniep/MemMachine          f72ff3e [main]
~/src/github.com/ChristianKniep/MemMachine-cleanup  4481a17 [knowledge_graph]

The second stack changes the ports using the .env file.

It will not start b/c the container name is already used. Second issue is going to be that the network name is used as well.

Expected behavior

Starting a stack without an explicit network defined will put all containers in a dedicated network anyways.
Instead of using docker exec which kinda needs a stable name, one can use docker-compose exec $service_name.

Environment

compose

Additional context

No response