Nicolas De loof
Nicolas De loof
I'm not in favor for more build flags added to the (already complex) `up` command. Considering the CI use-case, why not just rely on `build-args` set in compose.yaml, and set...
`watch` indeed takes place _after_ the compose file and related files have been parsed. It will neither re-create container with an updated config if you change anything in yaml. That's...
Please use `docker compose config` to see the parsed compose model and confirm override has been applied Trying to reproduce your issue I just get `network-a` removed from the model...
Can you please confirm issue persists with latest release (v2.23.0) ?
interpolation indeed only applies to values, not keys in a compose.yaml file maybe we should also support this where a user-defined key is expected (like `services` sub-elements) to be discussed...
ignoring the dependency was a bug, that we fixed. But as many did like you relied on this, we introduced `required` as a flag to mark a dependency as "nice...
Closing as a duplicate for https://github.com/compose-spec/compose-spec/issues/274
indeed, I missed the "logs" issue as a sub-issue here :)
`extends` used without a `file` require the referred service to be declared inside the same yaml document. With multi-document feature, a single file can have many, but there's no way...
wording indeed need to be updated. Compose has not been designed with multi-document yaml file in mind, this recent addition require some updates. Still, I need to double check this...