Repository navigation
Containers launch sequentially - can they be launched concurrently? #128
Description
Finding that using container-compose with a docker-compose.yml file containing 11 wiremock servers, each servers is launched sequentially, waiting for each to complete before starting to launch the next. This means the whole launch is pretty slow for multiple containers.
This is exacerbated by a timeout issue on 1.0.0 tagged version, but not on main, the launch time for 11 services is over 5 minutes as each waits for 30 seconds. But even on main the sequential launching takes ~23 seconds.
When launching the services with a custom bash script in parallel, this is reduced to 7 seconds.
Is it feasible to launch the services in parallel?
Activity
feat: add dependencyLevels scheduler for parallel `up` (Mcrich23#128)
feat: launch independent services concurrently in `up` (Mcrich23#128)
Mcrich23 commentedon Sep 9, 2026
Sorry for the slow response! I'm catching up on issues after being unable to work on open source for most of the summer.
Yes, independent services should be able to start concurrently. #144 and #145 work toward that, with #154 addressing a dependency issue it exposed. I want to verify dependency handling and failures before making it the default. Your 11-service example would be helpful for comparing startup time afterward if you don't mind providing some numbers and testing afterwards.
feat: add dependencyLevels scheduler for parallel `up` (#128) (#144)
feat: launch independent services concurrently in `up` (Mcrich23#128)