Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Tue, 25 Oct 2016 08:26:59 +0000 (UTC)
From: "Milind Chawre (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.13015010.1477384012000.76739.1477384019220@Atlassian.JIRA>
In-Reply-To: <JIRA.13015010.1477384012000@Atlassian.JIRA>
References: <JIRA.13015010.1477384012000@Atlassian.JIRA> <JIRA.13015010.1477384012012@arcas>
Subject: [jira] [Created] (MESOS-6480) Support for docker live-restore
 option in Mesos
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 25 Oct 2016 08:27:01 -0000

Milind Chawre created MESOS-6480:
------------------------------------

             Summary: Support for docker live-restore option in Mesos
                 Key: MESOS-6480
                 URL: https://issues.apache.org/jira/browse/MESOS-6480
             Project: Mesos
          Issue Type: Task
            Reporter: Milind Chawre


Docker-1.12 supports live-restore option which keeps containers alive during docker daemon downtime https://docs.docker.com/engine/admin/live-restore/
I tried to use this option in my Mesos setup And  observed this :
1. On mesos worker node stop docker daemon.
2. After some time start the docker daemon. All the containers running on that are still visible using "docker ps". This is an expected behaviour of live-restore option.
3. When I check mesos and marathon UI. It shows no Active tasks running on that node. The containers which are still running on that node are now scheduled on different mesos nodes, which is not right since I can see the containers in "docker ps" output because of live-restore option.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)