Nicolas De loof

The root cause for this behavior is that project name (which is used to filter resources) is inferred from parent folder for your compose file. If you use symlink `o`...

This is due to the compose file processing logic: compose.yaml is first parsed and interpolated, then compose select services to run and ignores others. To implement requested feature so that...

we can't as go is a typed language, so interpolation has to take place before we build a compose-go `Project` from yaml, so that (for illustration) port `80` is mapped...

There's no short term solution for this, Compose-go does a full compose.yaml parsing and resolution, and as such require all variables to be resolved. Changing this would be a full...

With https://github.com/docker/compose/pull/10284 you can now explicitly opt-in/out for dependent container to be restarted when a service is recreated.

see https://github.com/compose-spec/compose-spec/blob/master/spec.md#long-syntax-1

@andryushchenko see https://github.com/docker/compose/issues/10308#issuecomment-1447781552

@koniiiik using this example compose file: ```yaml services: service-1: image: nginx depends_on: service-2: condition: service_started restart: false service-2: image: nginx ``` ``` $ docker compose up -d [+] Running 2/2...

Compose converts short syntax `- /foo/bar` into a volume declaration, which relies on `mount` API, not `bind` where this label is automatically added by engine. For some reason, engine does...

indeed, thanks for clarification (it's hard to get a clear understanding on the many issues we have to address within my limited brain :P)