Nicolas De loof

`scale` command was deprecated in docker compose v1 for some reason (people left docker, so I can't ask them) it was re-introduced in [v2.22.0](https://github.com/docker/compose/releases/tag/v2.22.0) release with a subtle difference with...

We could indeed introduce `builder`, as a follow-up for https://github.com/compose-spec/compose-spec/issues/233

There's unfortunately no way to declare your `setup` service isn't actually a service, and termination is expected.

Such a feature in compose would make sense if `docker run` also has support for it, otherwise the user experience would be terribly confusing.

As you run `docker-compose -f some-compose-file down`, compose will parse the compose file and doing so will **only** consider the declared services, we have many users relying on this behavior...

@RETH666 can you please confirm this only applies to container created by docker compose, as requested by https://github.com/docker/compose/issues/10383#issuecomment-1481344482

Issue is perfectly valid, but then the question is: what would be a reasonable behavior when terminal height is not large enough for the amount of services we want to...

This is probably caused by https://github.com/docker/cli/pull/3900, which is included in latest release. Can you please confirm issue persists with docker compose v2.17.3 ?

Docker Compose by nature runs multiple docker API calls concurrently and can indeed quickly reach the ssh limits. Docker ssh support is actually implemented by running `docker system dial-stdio` on...

Have you tried enabling [ssh multiplexing](https://en.wikibooks.org/wiki/OpenSSH/Cookbook/Multiplexing) on your client? his would allow `docker compose` command to only rely on a single ssh session to access remote docker engine see https://github.com/docker/compose/issues/8191#issuecomment-1448646228...