You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 18, 2025. It is now read-only.
The rm only works with specifying the --force flag. This does not work as expected and as docker-compose does.
The --force works as expected when the container are still running. Even the force doesn't work as expected, docker-compose rm --force just don't ask for confirmation, but it will not remove running containers at all.
Steps to reproduce
Let's use the following docker-compose.yml :
web:
image: nginx
Using libcompose-cli
$ libcompose-cli up -d
# […]
$ libcompose-cli stop
# […]
$ libcompose-cli rm
# […]
FATA[0000] Will not remove all services without --force
Using docker-compose
$ docker-compose up -d
Creating compose_web_1
$ docker-compose stop
Stopping compose_web_1 ... done
$ docker-compose rm
Going to remove compose_web_1
Are you sure? [yN] y
Removing compose_web_1 ... done
The
rmonly works with specifying the--forceflag. This does not work as expected and asdocker-composedoes.TheEven the force doesn't work as expected,--forceworks as expected when the container are still running.docker-compose rm --forcejust don't ask for confirmation, but it will not remove running containers at all.Steps to reproduce
Let's use the following
docker-compose.yml:Using
libcompose-cliUsing
docker-compose