We don't provide users with any mechanism to remove/empty docker volumes — the equivalent of running docker volume rm my-vol. Right now they have to run that command directly. The problem then is that, since we don't clean up containers, the user will be presented with an error like the following:
Error response from daemon: remove count: volume is in use - [1fe52ecb91b5365149ed2df9a5771656e7d153d689f8bebf9799cd8a9ac2f6c5, 305bbe5d72517c47c85a9b4321087f688a2883c575d736e27930fce73e7c1775, 44f51a2d4f6d81509a0edef30c19cbc6dac0429c51d8a01508e618f02c1a6277]
I would propose we add a --remove-volumes flag to the exo stop command to handle this. Docker compose has a similar flag: https://docs.docker.com/compose/reference/down/
We don't provide users with any mechanism to remove/empty docker volumes — the equivalent of running
docker volume rm my-vol. Right now they have to run that command directly. The problem then is that, since we don't clean up containers, the user will be presented with an error like the following:I would propose we add a
--remove-volumesflag to theexo stopcommand to handle this. Docker compose has a similar flag: https://docs.docker.com/compose/reference/down/