[
https://issues.apache.org/jira/browse/MESOS-6480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15607412#comment-15607412
]
Milind Chawre edited comment on MESOS-6480 at 10/26/16 4:50 AM:
----------------------------------------------------------------
[~gilbert] Yes its seems duplicates. But my issue is slightly different, in my
case I am trying to run all infra services mesos master, mesos worker,
marathon, etc as docker containers and are not running as standalone services.
This ticket can be closed but while providing support to live-restore option
this case of all infra services running as docker containers should also be
considered.
was (Author: milindchawre):
Yes its seems duplicates. But my issue is slightly different, in my case I am
trying to run all infra services mesos master, mesos worker, marathon, etc as
docker containers and are not running as standalone services.
This ticket can be closed but while providing support to live-restore option
this case of all infra services running as docker containers should also be
considered.
> 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)
