You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Tim Harper (JIRA)" <ji...@apache.org> on 2017/04/10 02:57:42 UTC

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

Tim Harper created MESOS-7374:
---------------------------------

             Summary: 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: isolation
    Affects Versions: 1.2.0
            Reporter: Tim Harper
            Priority: Minor


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:
{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 at startup or launch time.



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