[jira] [Comment Edited] (MESOS-7007) filesystem/shared and --default_container_info broken since 1.1

["Pierre Cheynier (JIRA)" <ji...@apache.org>]

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

Pierre Cheynier edited comment on MESOS-7007 at 1/26/17 11:49 AM:
------------------------------------------------------------------

Here is how to reproduce the case with minimal custom setup:
{noformat}
# Define $MASTER and $WORKDIR
# Launch agent: 
/usr/sbin/mesos-slave --advertise_ip=127.0.0.1 --cgroups_hierarchy=/sys/fs/cgroup --containerizers=mesos,docker --default_container_info='{"type":"MESOS","volumes":[{"host_path":"tmp","container_path":"/tmp","mode":"RW"}]}' --default_role=default --isolation='cgroups/cpu,cgroups/mem,namespaces/pid,disk/du,filesystem/shared,filesystem/linux,docker/runtime' --master=$MASTER --port=5051 --strict --work_dir=$WORKDIR
# Create dummy file
touch /tmp/example
# Launch a container
mesos-execute --master='localhost:5050' --name=ls --command=ls
# List dir content, it's empty
ls /tmp


was (Author: pierrecdn):
Here is how to reproduce the case with minimal custom setup:
{noformat}
# Define $MASTER and $WORKDIR
# Launch agent: 
/usr/sbin/mesos-slave --advertise_ip=127.0.0.1 --cgroups_hierarchy=/sys/fs/cgroup --containerizers=mesos,docker --default_container_info='{"type":"MESOS","volumes":[{"host_path":"tmp","container_path":"/tmp","mode":"RW"}]}' --default_role=default --isolation='cgroups/cpu,cgroups/mem,namespaces/pid,disk/du,filesystem/shared,filesystem/linux,docker/runtime' --master=$MASTER --port=5051 --strict --work_dir=$WORKDIR
# Create dummy file
touch /tmp/example
# Launch a container
mesos-execute --master='localhost:5050' --name=ls --command=ls
# List dir content, it's empty
ls /tmp

> filesystem/shared and --default_container_info broken since 1.1
> ---------------------------------------------------------------
>
>                 Key: MESOS-7007
>                 URL: https://issues.apache.org/jira/browse/MESOS-7007
>             Project: Mesos
>          Issue Type: Bug
>          Components: agent
>    Affects Versions: 1.1.0
>            Reporter: Pierre Cheynier
>
> I face this issue, that prevent me to upgrade to 1.1.0 (and the change was consequently introduced in this version):
> I'm using default_container_info to mount a /tmp volume in the container's mount namespace from its current sandbox, meaning that each container have a dedicated /tmp, thanks to the {filesystem/shared} isolator.
> I noticed through our automation pipeline that integration tests were failing and found that this is because /tmp (the one from the host!) contents is trashed each time a container is created.
> Here is my setup: 
> * {{--isolation='cgroups/cpu,cgroups/mem,namespaces/pid,*disk/du,filesystem/shared,filesystem/linux*,docker/runtime'}}
> * {{--default_container_info='\{"type":"MESOS","volumes":\[\{"host_path":"tmp","container_path":"/tmp","mode":"RW"\}\]\}'}}
> I discovered this issue in the early days of 1.1 (end of Nov, spoke with someone on Slack), but had unfortunately no time to dig into the symptoms a bit more.
> I found nothing interesting even using GLOGv=3.
> Maybe it's a bad usage of isolators that trigger this issue ? If it's the case, then at least a documentation update should be done.
> Let me know if more information is needed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)