Skip to content

Conversation

@shin-
Copy link

@shin- shin- commented Mar 16, 2016

rm command now accepts a --all argument (shorthand -a) to remove one-off containers as well.

Going forward, the plan is to have this always be the case, hence a warning should be added for users when using rm

Options:
-f, --force Don't ask to confirm removal
-v Remove volumes associated with containers
-a, --all Also remove one-off containers
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if users know what "one-off" containers are, or if we should add "one-off containers created by docker-compose run".

shin- added 2 commits March 16, 2016 19:48
Signed-off-by: Joffrey F <joffrey@docker.com>
Signed-off-by: Joffrey F <joffrey@docker.com>
@shin- shin- force-pushed the 2774-off-one-offs branch from 668fb19 to 77457a7 Compare March 17, 2016 02:49
@dnephin dnephin added this to the 1.7.0 milestone Mar 17, 2016
def update_labels(cls, value, labels):
if value == cls.only:
labels.append('{0}={1}'.format(LABEL_ONE_OFF, "True"))
elif value == cls.exclude or value is False:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why value is False here? I think it might be safer to change the existing calls.

@dnephin
Copy link

dnephin commented Mar 21, 2016

Replaced by #3178

@dnephin dnephin closed this Mar 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants