[jira] [Closed] (MESOS-1657) docker containerizer should not delete container until gc runs

["Jay Buffington (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MESOS-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jay Buffington closed MESOS-1657.
---------------------------------

    Resolution: Duplicate

I got an error when I made 1656, didn't realize it actually got created.  This is a dup.

> docker containerizer should not delete container until gc runs
> --------------------------------------------------------------
>
>                 Key: MESOS-1657
>                 URL: https://issues.apache.org/jira/browse/MESOS-1657
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Jay Buffington
>
> When a task using the docker containerizer fails {{docker rm}} is immediately called and the container is removed.  I argue the container should not be removed until the garbage collector runs.  This gives users an opportunity to diagnose what went wrong.  MESOS-1652 will help with that, but there are other use cases where I want to inspect the state of the container that involve looking at files other than what was produced on stdout and stderr. 
> [~tnachen] discussed this on IRC.  See http://wilderness.apache.org/channels/?f=mesos/2014-07-31#1406842111



--
This message was sent by Atlassian JIRA
(v6.2#6252)