Project

General

Profile

Bug #3793

Updated by Ward Vandewege over 9 years ago

When we start Docker containers for jobs, we pass the @--rm=true@ option to Docker, which should remove the container image after it runs.    Unfortunately, Docker does not consistently remove the container image.    Over time, more and more will accumulate, until Docker's storage partition is full. 

 We haven't figured out any rhyme or reason to what containers aren't removed yet.    It happens across several different images, and it happens to containers whether they finish successfully (exit status 0) or not. 

 We need to decide on and implement additional container clean-up strategies—either as a complement or replacement to @--rm=true@. 

 There's a new option that is not in a released version that we should explore (force-rm). It should go into Docker 1.2.1

Back