You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Timothy Chen (JIRA)" <ji...@apache.org> on 2014/11/01 08:30:33 UTC
[jira] [Closed] (MESOS-1656) Do not remove docker container until
gc process runs
[ https://issues.apache.org/jira/browse/MESOS-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Chen closed MESOS-1656.
-------------------------------
commit 20b0225fcf1ed84c0f518ae51b856f43c044782f
Author: Timothy Chen <tn...@apache.org>
Date: Fri Oct 31 16:41:07 2014 -0700
Schedule docker containers for removal.
Instead of removing docker containers right after reap, schedule it to
be removed later.
Review: https://reviews.apache.org/r/26861
> Do not remove docker container until gc process runs
> ----------------------------------------------------
>
> Key: MESOS-1656
> URL: https://issues.apache.org/jira/browse/MESOS-1656
> Project: Mesos
> Issue Type: Improvement
> Components: containerization
> Reporter: Jay Buffington
> Assignee: Timothy Chen
>
> The current docker containerizer implementation that is up for review at https://reviews.apache.org/r/23771/ does a {{docker rm}} as soon as a task fails. This makes debugging difficult, if not impossible. MESOS-1652 will aid with this, but it does not address the use case of diagnosing a failure which involves inspecting the state of a container.
> [~tnachen] and I discussed this on IRC, see http://wilderness.apache.org/channels/?f=mesos/2014-07-31#1406842111
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)