I would like to run A service (a database), then run Spring Boot maven plugin (that runs a Spring app that requires the previous database) and finally run the C service (that requires the app to be up).
I could achieve that order using multiple executions, but I couldn't find the way to run only A service at the first time because the up goal works on all the services in the compose and I couldn't use start goal since the compose is not up.
I tried to use something similar to <startServices> like <upServices> but I think that feature is missing. Since it is possible to execute "docker-compose up A", where A is a service, I think that it makes a lot of sense to include <upServices>.
Hi,
I have a docker compose with 2 services: A and B.
I would like to run A service (a database), then run Spring Boot maven plugin (that runs a Spring app that requires the previous database) and finally run the C service (that requires the app to be up).
I could achieve that order using multiple executions, but I couldn't find the way to run only A service at the first time because the
up
goal works on all the services in the compose and I couldn't usestart
goal since the compose is not up.I tried to use something similar to
<startServices>
like<upServices>
but I think that feature is missing. Since it is possible to execute "docker-compose up A", where A is a service, I think that it makes a lot of sense to include<upServices>
.Thanks in advance!