You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Zhongbo Tian (JIRA)" <ji...@apache.org> on 2016/12/15 09:37:00 UTC
[jira] [Updated] (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:all-tabpanel ]
Zhongbo Tian updated MESOS-6798:
--------------------------------
Description:
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"
was:
When making a volume into `/dev/shm`, the volume would be 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 would get an error for "No such file or directory"
> 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
> Reporter: Zhongbo Tian
>
> 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
(v6.3.4#6332)