[
https://issues.apache.org/jira/browse/MESOS-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16388251#comment-16388251
]
James Peach edited comment on MESOS-6555 at 3/20/18 4:53 PM:
-------------------------------------------------------------
| [r/66175|https://reviews.apache.org/r/66175] | Added isolator checks for
namespaces support. |
was (Author: jamespeach):
| [r/65932|https://reviews.apache.org/r/65932] | Added a generic mechanism to
check for isolator requirements. |
> Namespace 'mnt' is not supported
> --------------------------------
>
> Key: MESOS-6555
> URL: https://issues.apache.org/jira/browse/MESOS-6555
> Project: Mesos
> Issue Type: Bug
> Components: cgroups, containerization
> Affects Versions: 1.0.0, 1.2.3, 1.3.1, 1.4.1, 1.5.0
> Environment: suse11 sp3, kernal: 3.0.101-0.47.71-default #1 SMP Thu
> Nov 12 12:22:22 UTC 2015 (b5b212e) x86_64 x86_64 x86_64 GNU/Linux
> Reporter: AndyPang
> Assignee: James Peach
> Priority: Minor
> Fix For: 1.6.0
>
>
> the same code run in debain os,kernal version is '4.1.0-0' is ok; while in
> sus 11 sp3 it has error.
> {code:title=mesos-execute|borderStyle=solid}
> ./mesos-execute --command="sleep 100" --master=xxxx:xxx --name=sleep
> --docker_image=ubuntu
> I1105 11:26:21.090703 194814 scheduler.cpp:172] Version: 1.0.0
> I1105 11:26:21.092821 194837 scheduler.cpp:461] New master detected at
> master@xxxx:xxx
> Subscribed with ID 'fdb8546d-ca11-4a51-a297-8401e53b7692-0000'
> Submitted task 'sleep' to agent 'fdb8546d-ca11-4a51-a297-8401e53b7692-S0'
> Received status update TASK_FAILED for task 'sleep'
> message: 'Failed to launch container: Collect failed: Failed to setup
> hostname and network files: Failed to enter the mount namespace of pid
> 194976: Namespace 'mnt' is not supported
> ; Executor terminated'
> source: SOURCE_AGENT
> reason: REASON_CONTAINER_LAUNCH_FAILED
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
