[
https://issues.apache.org/jira/browse/MESOS-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isabel Jimenez updated MESOS-1570:
----------------------------------
Description:
When building Mesos inside a Docker container, it's for the moment impossible
to run tests even when you run Docker in --privileged mode. There is a test in
stout that sets all the namespaces and libcontainer does not support setting
'user' namespace (more information
[here|https://github.com/docker/libcontainer/blob/master/namespaces/nsenter.go#L136]).
This is the error:
{code:title=Make check failed test|borderStyle=solid}
[----------] 1 test from OsSetnsTest
[ RUN ] OsSetnsTest.setns
../../../../3rdparty/libprocess/3rdparty/stout/tests/os/setns_tests.cpp:43:
Failure
os::setns(::getpid(), ns): Invalid argument
[ FAILED ] OsSetnsTest.setns (7 ms)
[----------] 1 test from OsSetnsTest (7 ms total)
[ FAILED ] 1 test, listed below:
[ FAILED ] OsSetnsTest.setns
1 FAILED TEST
{code}
This can be disable as Mesos does not need to set 'user' namespace. I don't
know if Docker will support setting user namespace one day since it's a new
kernel feature, what could be the best approach to this issue? (disabling set
for 'user' namespace on stout, disabling just this test..)
was:
When building Mesos inside a Docker container, it's for the moment impossible
to run tests even when you run Docker in --privileged mode. There is a test in
stout that sets all the namespaces and libcontainer does not support setting
'user' namespace (more information
[here|https://github.com/docker/libcontainer/blob/master/namespaces/nsenter.go#L136].
This is the error:
{code:title=Make check failed test|borderStyle=solid}
[----------] 1 test from OsSetnsTest
[ RUN ] OsSetnsTest.setns
../../../../3rdparty/libprocess/3rdparty/stout/tests/os/setns_tests.cpp:43:
Failure
os::setns(::getpid(), ns): Invalid argument
[ FAILED ] OsSetnsTest.setns (7 ms)
[----------] 1 test from OsSetnsTest (7 ms total)
[ FAILED ] 1 test, listed below:
[ FAILED ] OsSetnsTest.setns
1 FAILED TEST
{code}
This can be disable as Mesos does not need to set 'user' namespace. I don't
know if Docker will support setting user namespace one day since it's a new
kernel feature, what could be the best approach to this issue? (disabling set
for 'user' namespace on stout, disabling just this test..)
> Make check Error when Building Mesos in a Docker container
> -----------------------------------------------------------
>
> Key: MESOS-1570
> URL: https://issues.apache.org/jira/browse/MESOS-1570
> Project: Mesos
> Issue Type: Bug
> Reporter: Isabel Jimenez
> Priority: Minor
>
> When building Mesos inside a Docker container, it's for the moment impossible
> to run tests even when you run Docker in --privileged mode. There is a test
> in stout that sets all the namespaces and libcontainer does not support
> setting 'user' namespace (more information
> [here|https://github.com/docker/libcontainer/blob/master/namespaces/nsenter.go#L136]).
> This is the error:
> {code:title=Make check failed test|borderStyle=solid}
> [----------] 1 test from OsSetnsTest
> [ RUN ] OsSetnsTest.setns
> ../../../../3rdparty/libprocess/3rdparty/stout/tests/os/setns_tests.cpp:43:
> Failure
> os::setns(::getpid(), ns): Invalid argument
> [ FAILED ] OsSetnsTest.setns (7 ms)
> [----------] 1 test from OsSetnsTest (7 ms total)
> [ FAILED ] 1 test, listed below:
> [ FAILED ] OsSetnsTest.setns
> 1 FAILED TEST
> {code}
> This can be disable as Mesos does not need to set 'user' namespace. I don't
> know if Docker will support setting user namespace one day since it's a new
> kernel feature, what could be the best approach to this issue? (disabling set
> for 'user' namespace on stout, disabling just this test..)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
