Proposal

Currently, the implementation uses by default the "diverged" recreate strategy for docker-compose setups, and doesn't provide a way to override that:

Does it make sense to also provide these as options?

The issue I am facing is when trying to start the compose setup incrementally, i.e. start a container, run some tests, start another container that uses the first one as a dependency and run some other tests. This gives me the following errors:

• if I specify the container dependencies as part of RunServices (deps), it fails with The container name "..." is already in use by container
• If I dont, I get the no such service: ... error

So, I guess if we have the Recreate and RecreateDependencies options exposed, that would help with this, and also allow for more flexible testing setups.