[
https://issues.apache.org/jira/browse/MESOS-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14148040#comment-14148040
]
Mohit Soni commented on MESOS-1790:
-----------------------------------
If a framework chooses to skip chown, then it becomes framework's
responsibility to ensure that the files in the archive upon expansion will be
owned by correct user. Otherwise, the files be inaccessible. I guess that's a
fair assumption, and should help solve resolve such issues.
Another not so simple solution might be to not skip chown, but rather provide
an explicit chmod/chown mechanism. Basically, framework can provide a
collection of permission object, each specifying a file/directory, user, group,
read, write, execute, sticky bits, etc. Although, the implementation might be
more complicated, and will impose an implicit assumption on mesos slave to be
run as root.
> Add "chown" option to CommandInfo.URI
> -------------------------------------
>
> Key: MESOS-1790
> URL: https://issues.apache.org/jira/browse/MESOS-1790
> Project: Mesos
> Issue Type: Improvement
> Reporter: Vinod Kone
> Labels: newbie
>
> Mesos fetcher always chown()s the extracted executor URIs as the executor
> user but sometimes this is not desirable, e.g., "setuid" bit gets lost during
> chown() if slave/fetcher is running as root.
> It would be nice to give frameworks the ability to skip the chown.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
