You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Chun-Hung Hsiao (JIRA)" <ji...@apache.org> on 2018/08/15 22:25:00 UTC

[jira] [Commented] (MESOS-6798) Volumes in `/dev/shm` overridden by mesos containerizer

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

Chun-Hung Hsiao commented on MESOS-6798:
----------------------------------------

[~jasonlai] Will you be able to find a shepherd for this ticket and land this in this week? Should we make this a 1.7.0 blocker?

> Volumes in `/dev/shm` overridden by mesos containerizer
> -------------------------------------------------------
>
>                 Key: MESOS-6798
>                 URL: https://issues.apache.org/jira/browse/MESOS-6798
>             Project: Mesos
>          Issue Type: Bug
>          Components: containerization
>    Affects Versions: 1.1.1, 1.2.0, 1.3.1, 1.4.1, 1.5.0
>            Reporter: Zhongbo Tian
>            Assignee: Jason Lai
>            Priority: Major
>
> When making a volume into `/dev/shm`, the volume is overridden by default mount point.
> For example:
> {code}
> mesos-execute --master=mesos-master --name=test --docker_image=busybox --volumes='[{"container_path":"/tmp/hosts", "host_path":"/etc/hosts", "mode":"RO"}]' --command="cat /tmp/hosts"
> {code}
> This will get an error for "No such file or directory"



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)