Hey! If I have several applications that run unit-test against third-party containers, can I run as many docker-composes? It feels like the only option, when it comes to running containers, is to merge all my docker-composes into one, spin it up first and then run pants, somehow dealing with parallelism. And how can I skip docker-compose if there are no changes to apps which unit-tests rely on services in docker-compose?

Hi! Can you explain a little more about your use-case? I'm not sure I understand how docker and Pants interact in this scenario

Hi! I have the following layout in my monorepo:

└── services
  ├── go-service-1
  │  └── docker-compose.yaml
  ├── py-service-1
  │  └── docker-compose.yaml
  └── py-service-2
    └── docker-compose.yaml

and each service has its own docker-compose that spin up it's own postgres instance to run a test framework against. I don't understand how I can do

docker-compose up

as a "pre-hook" before tests