[jira] [Updated] (MESOS-7374) Running DOCKER images in Mesos Container Runtime without `linux/filesystem` isolation enabled renders host unusable

["Vinod Kone (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MESOS-7374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kone updated MESOS-7374:
------------------------------
    Shepherd: Gilbert Song  (was: Jie Yu)

> Running DOCKER images in Mesos Container Runtime without `linux/filesystem` isolation enabled renders host unusable
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: MESOS-7374
>                 URL: https://issues.apache.org/jira/browse/MESOS-7374
>             Project: Mesos
>          Issue Type: Bug
>          Components: containerization
>    Affects Versions: 1.2.0
>            Reporter: Tim Harper
>            Assignee: Chun-Hung Hsiao
>            Priority: Critical
>              Labels: containerizer, mesosphere
>
> If I run the pod below (using Marathon 1.4.2) against a mesos agent that has the flags (also below), then the overlay filesystem replaces the system root mount, effectively rendering the host unusable until reboot.
> flags:
> - {{--containerizers mesos,docker}}
> - {{--image_providers APPC,DOCKER}}
> - {{--isolation cgroups/cpu,cgroups/mem,docker/runtime}}
> pod definition for Marathon:
> {code:java}
> {
>   "id": "/simplepod",
>   "scaling": { "kind": "fixed", "instances": 1 },
>   "containers": [
>     {
>       "name": "sleep1",
>       "exec": { "command": { "shell": "sleep 1000" } },
>       "resources": { "cpus": 0.1, "mem": 32 },
>       "image": {
>         "id": "alpine",
>         "kind": "DOCKER"
>       }
>     }
>   ],
>   "networks": [ {"mode": "host"} ]
> }
> {code}
> Mesos should probably check for this and avoid replacing the system root mount point at startup or launch time.



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