Nicolas De loof

> Are these variable names actually invalid Documentation is unclear, and it seems we will need to align with _de facto_ compose V1 behavior regarding this ambiguous syntax

You can select dotEnv file to be used by Compose using `docker compose --env-file xxx youcommand` We _could_ extend profile support to automatically select an alternate dotEnv file, but I...

env_file in compose.yaml is the one used to define container environment, not the one used to parse yaml and interpolate `$xx` variables.

@calavera can you please explain why this issue has been closed ? I'm looking into implementing a docker garbage collector, and this would be a big helper for this use-case.

@fs-sgujrati this will let you know last time it has been used to start a container, but you don't know how long this container has been running. Let's say you...

You're right about the tricky part. API to give "last use" status for an image will need to know - if image is in use by existing containers. In such...

Future of Docker Compose is taking place on the Go implementation to be bundled with the Docker CLI as a plugin, see https://github.com/docker/compose-cli

Compose v1 entered the End of Life process, you should switch to compose v2

environment variable interpolation uses bash style: `${USERPROFILE}` (no `env:` prefix) is this for a Windows container (not Linux container on Docker Desktop Windows)? Which version of docker compose are you...

I'm asking about `docker-compose --version` you use, `version: 3.4` actually isn't relevant (and can be fully removed if you use a recent compose release)