Description
Most compose subcommands support an optional list of services to operate with, instead of all compose services.
Is there a good reason why the down command behaves differently?
My use case:
Stop a single service of the compose stack, AND remove all corresponding named volumes with it.
A close workaround would be to use compose stop && compose rm -v - but this works only for anonymous volumes, not named volumes.
So in addition to the [SERVICE...] argument for compose down, maybe it would also be nice and consistent to have an additional flag for the compose rm to also include named volumes, when needed (not my use case).
Description
Most compose subcommands support an optional list of services to operate with, instead of all compose services.
Is there a good reason why the
downcommand behaves differently?My use case:
Stop a single service of the compose stack, AND remove all corresponding named volumes with it.
A close workaround would be to use
compose stop && compose rm -v- but this works only for anonymous volumes, not named volumes.So in addition to the [SERVICE...] argument for
compose down, maybe it would also be nice and consistent to have an additional flag for thecompose rmto also include named volumes, when needed (not my use case).