From: ludo@gnu.org (Ludovic Courtès)
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: guix-devel <guix-devel@gnu.org>, 21410@debbugs.gnu.org
Subject: Re: Environment containers
Date: Wed, 28 Oct 2015 16:56:40 +0100 [thread overview]
Message-ID: <87fv0v6l6v.fsf@gnu.org> (raw)
In-Reply-To: <CAJ=RwfZg+ytagyGM73FbT25Btagvxb+eAZn74-0pyx=OqGqkJA@mail.gmail.com> (David Thompson's message of "Wed, 28 Oct 2015 11:20:03 -0400")
"Thompson, David" <dthompson2@worcester.edu> skribis:
> On Wed, Oct 28, 2015 at 11:14 AM, Alex Vong <alexvong1995@gmail.com> wrote:
>> On 28/10/2015, Ludovic Courtès <ludo@gnu.org> wrote:
>>> Alex Vong <alexvong1995@gmail.com> skribis:
>>>
>>>> On 27/10/2015, Ludovic Courtès <ludo@gnu.org> wrote:
>>>
>>> [...]
>>>
>>>>> Do you still experience the test failures mentioned in that report? If
>>>>> not, could you email 21410@debbugs.gnu.org, specifying which commit
>>>>> works for you?
>>>>>
>>>> Yes, there are 4 tests still failing with the latest master branch
>>>> without unprivileged container.
>>>
>>> Which tests? Does tests/container.scm pass?
>>>
>> It doesn't pass if I run as unprivileged user. It passes if I run as
>> root. I will be mailing the test logs on another mail.
>
> This is because Debian doesn't let unprivileged users create user
> namespaces without explicitly overriding some configuration.
How could we determine whether this restriction is in place? That would
allow us to skip the test on these systems.
Ludo’.
next prev parent reply other threads:[~2015-10-28 15:56 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 1:27 Environment containers Thompson, David
2015-10-26 10:45 ` Daniel Pimentel
2015-10-26 12:16 ` Alex Vong
2015-10-26 14:33 ` Ludovic Courtès
2015-10-26 14:37 ` Taylan Ulrich Bayırlı/Kammer
2015-10-26 14:38 ` Thompson, David
2015-10-27 5:11 ` Alex Vong
2015-10-27 10:58 ` Ludovic Courtès
2015-10-28 13:10 ` Alex Vong
2015-10-28 14:45 ` bug#21410: " Ludovic Courtès
2015-10-28 15:14 ` Alex Vong
2015-10-28 15:20 ` Thompson, David
2015-10-28 15:56 ` bug#21410: " Ludovic Courtès
2015-10-28 15:56 ` Ludovic Courtès [this message]
2015-10-28 16:08 ` Thompson, David
2015-10-28 16:20 ` Alex Vong
2015-10-28 16:20 ` bug#21410: " Alex Vong
2015-10-29 19:24 ` Ludovic Courtès
2015-10-29 19:24 ` Ludovic Courtès
2015-10-29 19:25 ` Thompson, David
2015-11-20 14:51 ` bug#21410: " Ludovic Courtès
2015-11-20 14:51 ` Ludovic Courtès
2015-11-21 13:36 ` Alex Vong
2015-11-21 15:57 ` Ludovic Courtès
2015-11-21 15:57 ` Ludovic Courtès
2015-11-21 17:47 ` Mathieu Lirzin
2015-11-21 21:27 ` Ludovic Courtès
2015-11-23 15:08 ` Alex Vong
2015-11-21 21:27 ` Ludovic Courtès
2015-11-21 17:47 ` Mathieu Lirzin
2015-11-21 13:36 ` Alex Vong
2015-10-29 19:25 ` Thompson, David
2015-10-28 16:08 ` Thompson, David
2015-10-28 15:20 ` Thompson, David
2015-10-28 13:10 ` Alex Vong
2015-10-29 10:25 ` Taylan Ulrich Bayırlı/Kammer
2015-10-26 16:23 ` Christopher Allan Webber
2015-10-26 17:50 ` Thompson, David
2015-10-28 15:32 ` Ricardo Wurmus
2015-10-28 19:09 ` Efraim Flashner
2015-10-29 12:36 ` Thompson, David
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fv0v6l6v.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=21410@debbugs.gnu.org \
--cc=dthompson2@worcester.edu \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.