You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Jason Lai (JIRA)" <ji...@apache.org> on 2017/06/19 21:31:00 UTC

[jira] [Commented] (AURORA-1903) Allow for RootFs to be set for mesos filesystem tasks

    [ https://issues.apache.org/jira/browse/AURORA-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16054771#comment-16054771 ] 

Jason Lai commented on AURORA-1903:
-----------------------------------

Added another review board patch on top of https://reviews.apache.org/r/60212/ to address [~StephanErb]'s comments in https://reviews.apache.org/r/57524/

> Allow for RootFs to be set for mesos filesystem tasks
> -----------------------------------------------------
>
>                 Key: AURORA-1903
>                 URL: https://issues.apache.org/jira/browse/AURORA-1903
>             Project: Aurora
>          Issue Type: Task
>            Reporter: Zameer Manji
>            Assignee: Zameer Manji
>         Attachments: table.png
>
>
> Currently when a TaskConfig is for a Mesos container task and it has an image. We currently place the image as a volume mounted at {{taskfs}} in the sandbox. Thermos, or other executors are launched outside the image and then are expected to chroot into the {{taskfs}} directory.
> However I think it would be a fine addition to allow executors to set the {{image}} property of the Mesos container instead of putting the image as a volume. This enables some tasks to get around a limitation of the MesosContainerizer where certain container paths must already exist in the image and the host.
> See the [documentation|http://mesos.apache.org/documentation/latest/docker-volume/] for the table that describes this.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)