Nicolas De loof

nope, variables can be nested, which makes this way more complicated. Maybe _feasible_, but for a limited benefits. What do you rely on `config --no-interpolate` for ?

Issue is caused by navigation menu. A simple workaround is to run `docker compose up --menu=false & pgid=$!`

I can't reproduce. After initial pull, `--pull=missing` (which is the default value) doesn't trigger image pull Please check `docker image inspect phpmyadmin`

Can you please try to reproduce with a minimal example, or share your compose files for further analysis ?

bash variable support is way more elaborated that compose one 😅 also, AFAICT bash never warn you about empty variable, just defaults to blank, so the comparison is pretty limited...

My bad, flag is well supported, just need to be set after the run command, not as argument: ``` $ docker compose run --remove-orphans SERVICE ```

Why don't you set build args in your compose file ? (https://github.com/compose-spec/compose-spec/blob/main/build.md#args) There's no way to guess how image has been built and the flag used by a previous command...

That's an interesting proposal, some thoughts: - Compose would need to know about the current service node to resolve `toml.services.images`, this is a significant change in the parser - Your...

Closing as "not planned" While this is an interesting proposal, this would require a full redesign of the compose file parser For those interested in such a feature, better implement...

I tried to reproduce with a simple config: first started services without a shared volume: ```yaml services: backend: image: nginx frontend: image: nginx ``` then updated config to add a...