From: "Ludovic Courtès" <ludo@gnu.org>
To: dan <i@dan.games>
Cc: 59069@debbugs.gnu.org, David Thompson <davet@gnu.org>
Subject: bug#59069: `guix shell -CN' failed to access GPU
Date: Thu, 10 Nov 2022 16:49:00 +0100 [thread overview]
Message-ID: <87o7teg68j.fsf@gnu.org> (raw)
In-Reply-To: <87zgcyu99s.fsf@dan.games> (dan's message of "Thu, 10 Nov 2022 23:08:41 +0800")
Hi!
(Cc: Dave Thompson, the original author of this code.)
As you pointed out on IRC, the problem is that ‘guix shell -C’ provides
/sys whereas ‘guix shell -CN’ doesn’t.
This stems from this call in (gnu build linux-container), which has
always been there:
(mount-file-systems root mounts
#:mount-/proc? (memq 'pid namespaces)
#:mount-/sys? (memq 'net
namespaces))
This is explained a few lines above:
;; A sysfs mount requires the user to have the CAP_SYS_ADMIN capability in
;; the current network namespace.
(when mount-/sys?
(mount* "none" (scope "/sys") "sysfs"
(logior MS_NOEXEC MS_NOSUID MS_NODEV MS_RDONLY)))
As you noticed with ‘--expose=/sys’, bind-mounting /sys doesn’t work
either (‘mount’ fails with EINVAL).
Not sure what to do. Thoughts?
Ludo’.
prev parent reply other threads:[~2022-11-10 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 6:11 bug#59069: `guix shell -CN' failed to access GPU dan
2022-11-10 9:45 ` Ludovic Courtès
2022-11-10 15:08 ` dan
2022-11-10 15:49 ` Ludovic Courtès [this message]
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=87o7teg68j.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=59069@debbugs.gnu.org \
--cc=davet@gnu.org \
--cc=i@dan.games \
/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).