Nicolas De loof
Nicolas De loof
I mean, you're asking to get the equivalent of `docker compose down` for your usage, so my question: why not just use it? Run your test suite using `docker compose...
or `docker compose up test --abort-on-container-exit` so when test container complete the stack is stopped
> it would tear down everything it had to start this is not compose philosophy. You describe a desired state as yaml, compose creates resources accordingly and remove (all of)...
That's an interesting use case. There's no simple solution for now to cover this, but I had in mind we could introduce support for "composition of compose projets" for large...
see https://github.com/compose-spec/compose-spec/pull/363
Requested feature is a corner-case that would hardly align with other compose commands. if we consider `run --prune` should remove resources, why would it ignore pre-existing resources and only remove...
"orphan containers" are _both_ containers associated with a service that is undefined in the current compose.yaml (as warning message says) but also older containers ran by `docker compose run`. This...
Actually `docker compose exec` should not target one-off containers, this seems like a bug we introduced, maybe some user start to rely on so #11995 could be a reasonable workaround
> There must be a naive splitting of the volume string by : indeed, as variable syntax has many subtle rules, it makes it hard to split string without actual...
Closing as "not planned". There's unfortunately no way to manage ambiguous `:` in short volume syntax when interpolation is disabled.