mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre Cheynier (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-7069) The linux filesystem isolator should set mode and ownership for host volumes.
Date Wed, 08 Feb 2017 14:54:42 GMT

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

Pierre Cheynier commented on MESOS-7069:
----------------------------------------

Hi,
Not sure if I do a mistake, but doing the same with only {{filesystem/linux}} rather than
{{filesystem/linux,filesystem/shared}} I have different behavior in 1.1...
Basically, my volume configured via `--default_container_info` is now a bind mount and not
a pure mount (meaning that the /tmp use-case described is broken in my case).
I'm using both containerized and not containerized tasks AND always set a user to my tasks.

> The linux filesystem isolator should set mode and ownership for host volumes.
> -----------------------------------------------------------------------------
>
>                 Key: MESOS-7069
>                 URL: https://issues.apache.org/jira/browse/MESOS-7069
>             Project: Mesos
>          Issue Type: Bug
>          Components: isolation
>            Reporter: Gilbert Song
>              Labels: filesystem, linux, volumes
>
> If the host path is a relative path, the linux filesystem isolator should set the mode
and ownership for this host volume since it allows non-root user to write to the volume. Note
that this is the case of sharing the host fileysystem (without rootfs).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message