Nicolas De loof
Nicolas De loof
To better cover this scenario, it seems to be we should define a new depends_on condition dedicated to build requirements, i.e. ```yaml services: base: build: . extened: build: context: extended...
@pebo can you provide a simple example to reproduce this issue? Docker Compose run builds in `depends_on` order to address this need (while dependency might not be required at runtime,...
code looks good, but I'm not fan for adding an option that only applies to the `--config` pseudo-command (which should be a subcommand), as this would be confusing and not...
A possible issue with my proposed solution is that `compose config` accept a list of `services` as arguments, and introducing sub-commands would conflict with this usage or forbid use of...
Got it, make sense.
I tend to agree. Agile != "let's add random stuff and change our mind any time", especially when it comes to UX. Once we introduce a new flag, it will...
@thaJeztah this seems to be the same race condition issue we discussed on https://github.com/docker/compose/pull/10067 Shall we apply a comparable workaround to start containers sequentially to workaround race condition in libnetwork?
@robertoporceddu that's weird you get this fixed this way, as Docker Compose doesn't use `update_config` to create containers
`8000-8010:80` syntax already tells engine to select a random available port within the 8000-8010 range since https://github.com/docker/compose/pull/10067 (v2.14.1) we start containers sequentially to workaround race condition in engine selecting such...