[
https://issues.apache.org/jira/browse/MESOS-6480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15615551#comment-15615551
]
haosdent commented on MESOS-6480:
---------------------------------
We may use {{docker run -d}} first and then use {{docker logs --follow}} to
make the log redirect to sandbox stdout/stderr.
> 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)
