Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mark deleted containers as deleted #1815

Closed
cjellick opened this issue Aug 17, 2015 · 1 comment
Closed

Mark deleted containers as deleted #1815

cjellick opened this issue Aug 17, 2015 · 1 comment
Assignees
Labels
area/agent Issues that deal with the Rancher Agent kind/enhancement Issues that improve or augment existing functionality

Comments

@cjellick
Copy link

In our initial implementation of native docker integration, we made the decision that if rancher-agent was down and containers got deleted, when rancher agent came back up, we would not mark those containers as deleted in rancher. Instead, we marked them as stopped.

This confuses users. @ibuildthecloud referenced some specific companies/users that were confused by it.

We want to change the behavior so that rancher marks such containers as deleted.

@deniseschannon deniseschannon added kind/enhancement Issues that improve or augment existing functionality status/resolved area/agent Issues that deal with the Rancher Agent labels Aug 20, 2015
@sangeethah
Copy link
Contributor

Tested with server version - v0.34.0-rc3

container1 in "stopped" state
container2 in "running" state.

From host:
stop rancher agent.
delete container1
delete container 2.

start rancher agent,

When host gets to "active" , state both "container1" and "container2" get deleted and purged in rancher-server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/agent Issues that deal with the Rancher Agent kind/enhancement Issues that improve or augment existing functionality
Projects
None yet
Development

No branches or pull requests

3 participants