[ https://issues.apache.org/jira/browse/MESOS-6480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16942893#comment-16942893 ]
Andrei Budnik commented on MESOS-6480: -------------------------------------- design doc: [https://docs.google.com/document/d/1JeLTr9L31S8eIg-6xpjedIUKvnfNake0kPTzxEwdUdI] > 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 > Priority: Major > > 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 (v8.3.4#803005)