unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Garlick <pgarlick@tourbillion-technology.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 31977@debbugs.gnu.org
Subject: bug#31977: clone tests fail on CentOS 7
Date: Mon, 21 Dec 2020 15:29:27 +0000	[thread overview]
Message-ID: <8738bc1a86f5af35a9aa79e3e7da0e4fac15348e.camel@tourbillion-technology.com> (raw)
In-Reply-To: <867dpervs5.fsf@gmail.com>

Hi Simon,

> If I understand well your message:
> 
>         Files:
>         a) '/proc/self/ns/user' exists
>         b) '/proc/sys/kernel/unprivileged_userns_clone' does not exist.

Yes, this is the case on CentOS.  

So testing for the existence of the unprivileged_userns_clone file is
an insufficent test for unprivileged user namespaces.  We have learnt
that trying to create the file as a dummy file does not work, since the
/proc/sys/kernel directory is read-only even for root.

So the current 'unprivileged-user-namespace-supported?' function in
gnu/build/linux-container.scm really only works for Debian-derived
systems.  Other systems, that co not create the
unprivileged_userns_clone file, differ in their default configurations.
CentOS, for example, disables the feature.  However, Guix System
enables it.

It has been suggested that the feature itself should be tested, instead
of relying on the /proc filesystem.  This could well be a better idea
and I gather from the thread that this idea is being worked on.  I can
test on CentOS when a new patch is available.

Best regards,

Paul. 





  reply	other threads:[~2020-12-21 15:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-26 14:16 bug#31977: clone tests fail on CentOS 7 Paul Garlick
2020-12-01 18:12 ` zimoun
2020-12-02 18:08   ` Paul Garlick
2020-12-03 16:34   ` Paul Garlick
2020-12-07  0:54     ` zimoun
2020-12-19  9:26       ` zimoun
2020-12-21 15:29         ` Paul Garlick [this message]
2022-10-08 14:30           ` zimoun
2022-11-03  9:47             ` zimoun

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8738bc1a86f5af35a9aa79e3e7da0e4fac15348e.camel@tourbillion-technology.com \
    --to=pgarlick@tourbillion-technology.com \
    --cc=31977@debbugs.gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).