You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "haosdent (JIRA)" <ji...@apache.org> on 2015/04/19 15:04:58 UTC

[jira] [Commented] (MESOS-2603) Permissions and ownership of persistent volumes are not set correctly.

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

haosdent commented on MESOS-2603:
---------------------------------

After set the owner of the persistent volume to be frameworkInfo.user, I think we could provide api for framework to add read/write permissions for special user.

> Permissions and ownership of persistent volumes are not set correctly.
> ----------------------------------------------------------------------
>
>                 Key: MESOS-2603
>                 URL: https://issues.apache.org/jira/browse/MESOS-2603
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Jie Yu
>
> Right now, we don't change the owner/group of the persistent volume created by slave and the default permission is 755. If slave is running under root, a non-root task won't be able to create files in the persistent volume.
> One way is to set the owner/group of the persistent volume to be frameworkInfo.user. But what if the commandInfo of the executor uses a different user?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)