[ https://issues.apache.org/jira/browse/MESOS-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14715548#comment-14715548 ]
Jie Yu commented on MESOS-3310: ------------------------------- commit 33058278e4839fdfaf65b2adc7785e61d74b6775 Author: Jie Yu <yujie....@gmail.com> Date: Mon Aug 24 16:22:08 2015 -0700 Added a filesystem isolator test to test image in volume while the container root filesystem is also specified. Review: https://reviews.apache.org/r/37738 commit 40638c5413266f4a4d5117cde225247ad19b2f55 Author: Jie Yu <yujie....@gmail.com> Date: Mon Aug 24 15:55:11 2015 -0700 Refactored filesystem isolator tests to allow multiple rootfses. Review: https://reviews.apache.org/r/37735 commit da2dfab8c77ae583eff1a5ce54f23f4b17831976 Author: Jie Yu <yujie....@gmail.com> Date: Mon Aug 24 14:23:27 2015 -0700 Used recursive bind mounts for volumes. Review: https://reviews.apache.org/r/37734 commit 347d51ceca849cc26b9ada8f1014e4c578eeb47b Author: Jie Yu <yujie....@gmail.com> Date: Mon Aug 24 12:44:12 2015 -0700 Added support for preparing images specified in volumes. Review: https://reviews.apache.org/r/37726 > Support provisioning images specified in volumes. > ------------------------------------------------- > > Key: MESOS-3310 > URL: https://issues.apache.org/jira/browse/MESOS-3310 > Project: Mesos > Issue Type: Task > Reporter: Jie Yu > Assignee: Jie Yu > > This is related to MESOS-3095 and MESOS-3227. > The idea is that we should allow command executor to run under host > filesystem and provision the filesystem for the user. The command line > executor will then chroot into user's root filesystem. > This solves the issue that the command executor is not launchable in the user > specified root filesystem. > The design doc is here: > https://docs.google.com/document/d/16hyLVRL0nz-KBts1J5stGyxZPniFPbPbs7R-ZRQVCH4/edit?usp=sharing -- This message was sent by Atlassian JIRA (v6.3.4#6332)