[
https://issues.apache.org/jira/browse/MESOS-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14594449#comment-14594449
]
Adam B commented on MESOS-2603:
-------------------------------
Or we could just chown the volume over to the commandInfo.user each time a new
executor mounts it. Why wouldn't that work?
Bumping this up to Critical, since it is essential for the persistent volumes
feature.
> 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)
