Nicolas De loof
Nicolas De loof
**What I did** example use for https://github.com/compose-spec/compose-go/pull/506
**What I did** some commands like `docker compose logs SERVICE` don't have to validate dependencies are well defined in project model **Related issue** fixes https://github.com/docker/compose/issues/10993 **(not mandatory) A picture of...
**What this PR does / why we need it**: `networks` section has description for "host or none" which actually applies to network_mode in services, not network top level element.
**What this PR does / why we need it**: introduce `depends_on.service` to define target service. Defaults to mapping key, but could be overridden, typically using a variable. **Which issue(s) this...
**What this PR does / why we need it**: introduce `remove` to configure runtime autoremove for service containers **Which issue(s) this PR fixes**: Fixes https://github.com/docker/compose/issues/10688
**What this PR does / why we need it**: introduce `external` service attribute to declare a service as "managed outside compose lifecycle" **Which issue(s) this PR fixes**: See https://github.com/compose-spec/compose-spec/issues/73
**What is the problem you're trying to solve** On can easily push all images involves in a Compose application, but still need to find another way to share the compose.yaml...
**What is the problem you're trying to solve** "init containers" is a common and useful pattern to implement environment setup for a service container. There's no such concept in the...
if compose file is configured not to attach to a service, `logs` command should not include this service closes https://github.com/docker/compose/issues/11529
**What I did** make code simpler relying on compose-go functions