compose/tests/fixtures/abort-on-container-exit-dep.../docker-compose.yml

version: "2.0"
services:
  simple:
    image: busybox:1.31.0-uclibc
    command: top
    depends_on:
      - another
  another:
    image: busybox:1.31.0-uclibc
    command: ls /thecakeisalie
Support attaching to dependencies on up When using the 'up' command, only services listed as arguments are attached to, which can be very different to the 'no argument' case if a service has many and deep dependencies: - It's not clear when dependencies have failed to start. Have to run 'compose ps' separately to find out. - It's not clear when dependencies are erroring. Have to run 'compose logs' separately to find out. With a simple setup, it's possible to work around theses issue by using the 'up' command without arguments. But when there are lots of 'top-level' services, with common dependencies, in a single config, using 'up' without arguments isn't practical due to resource limits and the sheer volume of output from other services. This introduces a new '--attach-dependencies' flag to optionally attach dependent containers as part of the 'up' command. This makes their logs visible in the output, alongside the listed services. It also means we benefit from the '--abort-on-container-exit' behaviour when dependencies fail to start, giving more visibility of the failure. Signed-off-by: Ben Thorner <ben.thorner@digital.cabinet-office.gov.uk> 2019-10-08 18:14:23 +02:00			`version: "2.0"`
			`services:`
			`simple:`
			`image: busybox:1.31.0-uclibc`
			`command: top`
			`depends_on:`
			`- another`
			`another:`
			`image: busybox:1.31.0-uclibc`
			`command: ls /thecakeisalie`