[
https://issues.apache.org/jira/browse/MESOS-8688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16767095#comment-16767095
]
Qian Zhang commented on MESOS-8688:
-----------------------------------
This issue will be resolved by MESOS-8810.
> Persistent volumes under taskgroup non-root user may not be writable if
> executor user under root.
> -------------------------------------------------------------------------------------------------
>
> Key: MESOS-8688
> URL: https://issues.apache.org/jira/browse/MESOS-8688
> Project: Mesos
> Issue Type: Bug
> Components: executor
> Reporter: Gilbert Song
> Priority: Major
> Labels: default-executor, persistent-volumes
>
> If the executor and the task are with different users, the persistent volume
> may not be writable. For example, in the case of the default executor
> consuming persistent volumes, if the executor is root user (from the
> frameworkinfo) and the task is non-root user (from the commandinfo), the
> persistent volume would be owned by the root which is unwritable for the task.
> This is caused by the persistent volume support for nested container with the
> default executor is a workaround (rely on the default executor specifying a
> sandbox_path volume). We should figure out a correct way to support
> persistent volume primitive for nested containers.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
