I am using the
Some commands like
up -d service_name or
start service_name are returning right away and this is pretty useful if you don't want the containers running to depend on the state of the shell, like they do with regular
up service_name. The one use-case is running it from some kind of continious integration/delivery server.
But this way of running/starting services does not provide any feedback about the actual state of the service afterwards.
The Docker Compose CLI reference for
up command does mention the relevant option, but, as for version
1.7.1, it is mutually exclusive with
--abort-on-container-exit Stops all containers if any container was stopped. *Incompatible with -d.*