From: "Sébastien Lerique" <sl@eauchat.org>
To: guix-science@gnu.org
Cc: "Ludovic Courtès" <ludovic.courtes@inria.fr>,
zimoun <zimon.toutoune@gmail.com>
Subject: Re: Introducing Guix to HPC at my institution
Date: Fri, 26 Mar 2021 17:22:43 +0900 [thread overview]
Message-ID: <877dlucsur.fsf@eauchat.org> (raw)
In-Reply-To: <87r1kdci49.fsf@eauchat.org>
Hi Ludo, Simon, all,
> Will be back once I have some progress or more questions.
It turns out the HPC cluster I have access to has user namespaces
activated \o/, so I'm looking into getting things running as an
unpriviliged user to show other people how useful Guix can be
(before approaching higher levels in the administration).
I have been through the following notes:
https://hpc.guix.info/blog/2017/09/reproducibility-and-root-privileges/
https://hpc.guix.info/blog/2017/10/using-guix-without-being-root/
http://issues.guix.gnu.org/34494
and am now following Guix's binary installation inside a user
namespace. After decompressing the binary distribution of guix
inside `~/local-guix`, my naïve next step was `unshare -mrf chroot
~/local-guix
gnu/store/mmhimfwmmidf09jw1plw3aw1g1zn2nkh-bash-static-5.0.16/bin/bash`.
But my knowledge of linux namespaces is hindering my next steps
:). A few questions:
- after setting $GUIX_PROFILE and sourcing
`/root/.config/guix/current`, running `guix` warns with:
GC Warning: pthread_getattr_np or pthread_attr_getstack failed
for main thread
GC Warning: Couldn't read /proc/stat
The first warning I don't know what to do with. About the
second: should I be binding `/proc` somehow?
- is it possible to create build users inside the user-namespaced
chroot?
- last but not least, how would I go about sharing this setup with
other users on the cluster? Ideally I would like to have a
non-priviliged build daemon that other users can call on. (Is
there such a thing as kernel group namespaces?)
Is this the right way to go for running guix without being root,
or is there a better way?
Thanks for any guidance you might provide!
Best,
Sébastien
next prev parent reply other threads:[~2021-03-26 8:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 3:12 Introducing Guix to HPC at my institution Sébastien Lerique
2021-03-15 13:47 ` zimoun
2021-03-16 1:54 ` Sébastien Lerique
2021-03-16 8:06 ` zimoun
2021-03-16 9:05 ` Ludovic Courtès
2021-03-18 2:26 ` Sébastien Lerique
2021-03-26 8:22 ` Sébastien Lerique [this message]
2021-03-29 12:03 ` Ludovic Courtès
2021-03-30 1:54 ` Sébastien Lerique
2021-03-30 7:21 ` Ludovic Courtès
2021-03-31 5:23 ` Sébastien Lerique
2021-04-01 8:35 ` Ludovic Courtès
2021-04-01 14:34 ` Sébastien Lerique
2021-04-10 20:43 ` Ludovic Courtès
2021-04-12 1:21 ` Sébastien Lerique
2021-04-12 12:43 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2021-03-29 0:45 Sébastien Lerique
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=877dlucsur.fsf@eauchat.org \
--to=sl@eauchat.org \
--cc=guix-science@gnu.org \
--cc=ludovic.courtes@inria.fr \
--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 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.