Skip to content
This repository has been archived by the owner on Jun 16, 2021. It is now read-only.

The rm command always require --force #129

Closed
vdemeester opened this issue Dec 26, 2015 · 0 comments
Closed

The rm command always require --force #129

vdemeester opened this issue Dec 26, 2015 · 0 comments

Comments

@vdemeester
Copy link
Collaborator

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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant