Custom compose project name not handled properly

[NathanBaulch]

Quite a few areas of lazydocker are broken when working with compose projects that were started with a custom project name, eg docker compose -p foo up -d. It looks like some of these can be fixed by conditionally adding the -p flag to the command templates (project name context is not always available):

commandTemplates:
  dockerCompose:  docker compose
  restartService: '{{ .DockerCompose }} -p {{ .Service.Container.ProjectName }} restart {{ .Service.Name }}'
  startService:   '{{ .DockerCompose }} -p {{ .Service.Container.ProjectName }} start {{ .Service.Name }}'
  ...

However project name context is not passed to the bulk commands so I wasn't able to "fix" those in the same way.

It seems like we either need to implement a -p flag similar to -f or find a reliable way to discover and apply custom project names internally. Unfortunately there is no docker-compose ls and docker-compose config doesn't look at what's actually running. Maybe the existing strategy of looking for a com.docker.compose.project label could be moved out of the gui package?

By the way, I'm aware of the top level name element introduced earlier in the year but the spec specifically says this should be overridable (-p flag or COMPOSE_PROJECT_NAME env var).

Actually, that's probably a much better workaround than modifying all the templates - just make sure COMPOSE_PROJECT_NAME is set in the current shell. This seems to work reliably in my project COMPOSE_PROJECT_NAME=foo lazydocker. It doesn't look like lazydocker supports dotenv files, so perhaps the popular godotenv package could be integrated?

[amenk]

We have all our docker compose files in projectXYZ/docker and a .env file with the COMPOSE_PROJECT_NAME
So each project is detected as docker

The suggested workaround COMPOSE_PROJECT_NAME=myproject lazydocker still displays docker

[vlipovetskii]

@amenk

The suggested workaround COMPOSE_PROJECT_NAME=myproject lazydocker still displays docker

These are the two approaches that worked for me:

• export COMPOSE_PROJECT_NAME=... + if it's required -f "custom-compose.yml" lazydocker option must be used.
• name: "${COMPOSE_PROJECT_NAME}" in the top of the compose.yml + if it's required -f "custom-compose.yml" lazydocker option must be used.

The panel Services is displayed.
The panel Docker-Compose Config displays name: correct project name
The panel Project still dispalys the project directory name.

If -f "custom-compose.yml" specified without export COMPOSE_PROJECT_NAME=... or name: "${COMPOSE_PROJECT_NAME}" the panel Services is displayed, but The panel Docker-Compose Config displays name: invalid project name

[jesseduffield]

Should be fixed by #774 (v0.25.0). Let me know if the issue persists: that PR was intended to fix a bunch of issues in one go.

[amenk]

@jesseduffield it seems to work, thanks!