-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
docker containers are not removed when status is dead #973
Comments
@g0t4 So Nomad does garbage collection of allocations some time after a job completes. The idea behind keeping the allocations after they have completed for some time is to allow users to inspect the allocation once they have finished in case they want to debug something. I think the time is roughly four hours now. We are going to do more aggressive garbage collection on the client side when there is pressure for resources. cc/ @dadgar Can you confirm? |
Ok yeah, I was wondering if it's GCd, can we add a setting to nuke them on Can I run GC myself and force nomad to clean them up? On Thursday, March 24, 2016, Diptanu Choudhury notifications@github.com
|
Running |
I setup a cron job for now On Wednesday, April 6, 2016, K.C. Wong notifications@github.com wrote:
|
This is going to be fixed for 0.3.2, some tests are failing so I haven't merged the branch with the fix. Few more days! |
Thanks for quickly getting to this On Thu, Apr 7, 2016 at 12:44 AM, Diptanu Choudhury <notifications@github.com
|
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
v0.3.1
Operating system and Environment details
centos 7 3.10.0-327.10.1.el7.x86_64
Docker version 1.10.3, build 20f81dd
Issue
When I call nomad stop on a batch job, containers associated with dead allocations are not cleaned up. However, if the allocation is still running, the container is cleaned up.
Is it possible Kill is only called on running allocations and thus cleanup only happens for running containers?
Reproduction steps
docker ps -a
, the container will be there with a status of exiteddocker ps -a
, there won't be any containers, in this case the container is cleaned up.The text was updated successfully, but these errors were encountered: