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

["Julien Pepy (JIRA)" <ji...@apache.org>]

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

Julien Pepy commented on MESOS-7007:
------------------------------------

Hi,

I was looking into rebasing [~chhsia0]'s patch (https://reviews.apache.org/r/58980/) on v1.4.0, but as [~naelyn] notcied the codebase has diverged a lot since May, mostly due to MESOS-7449.

So here is a new slightly different patch: https://reviews.apache.org/r/63598/
It fills ContainerInfo from the Executor, when present, so that it become the default if no ContainerInfo is present in TaskInfo (whether using a container image or a command). It seemed logical, since agents can be configured with default ContainerInfo to pass to the Executor.
It has been tested successfully on v1.4.0.
Is it possible to integrate it to this ticket? Thanks!

> 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, 1.2.0
>            Reporter: Pierre Cheynier
>            Assignee: Chun-Hung Hsiao
>              Labels: storage
>
> 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.4.14#64029)