[
https://issues.apache.org/jira/browse/MESOS-7374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Harper updated MESOS-7374:
------------------------------
Description:
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.
was:
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.
> 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 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)
