From: ludo@gnu.org (Ludovic Courtès)
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Unprivileged /gnu/store with PRoot - or relocate
Date: Sat, 13 May 2017 16:12:13 +0200 [thread overview]
Message-ID: <8737c83kxu.fsf@gnu.org> (raw)
In-Reply-To: <20170513053859.GA19841@thebird.nl> (Pjotr Prins's message of "Sat, 13 May 2017 07:38:59 +0200")
Hello!
Pjotr Prins <pjotr.public12@thebird.nl> skribis:
> I explored this and actually built Nix/Guix on proot in the past for the
> same reasons
>
> https://github.com/pjotrp/nix-no-root
Right, thanks for the reminder!
Back then the target was mostly to run a full Nix/Guix under PRoot,
right? I suppose running guix-daemon & co. under PRoot would be
terribly slow, especially when building stuff.
> Mind, it *is* slow. That is why I came up with relocatable Guix which
> works much better. No performance loss. Just an extra installation
> step. Relocatable Guix works great, but it requires effort to make it
> user friendly. We can automate creating relocatable packages with guix
> pack. All it needs is an additional installer that rewrites the paths.
> The other limitation is that the installer prefix can be no longer
> than ~50 characters because it gobbles up the Guix store path + hash.
>
> I have written all the code for that. The installer is fast.
>
> Anyone interested in that type of solution? We can make it work, even
> as automated builds. I think it would be great for HPC and can even be
> part of non-root packagers, such as brew and conda.
Definitely. As discussed before, my personal preference for the
technical solutions to this problem is, in this order:
1. user namespaces (unfortunately rarely available, at least on HPC);
2. PRoot, provided the performance is okay for the target workload;
3. relocation as you presented it at FOSDEM.
When #1 is available that’s good. In other cases, one has to choose
between #2 and #3 depending on performance and other tradeoffs.
Each of these approaches has its pros and cons. We all know that the
one true solution to file system virtualization is GNU/Hurd… but we’re
not there yet! :-)
Ludo’.
next prev parent reply other threads:[~2017-05-13 14:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 15:53 Unprivileged /gnu/store with PRoot Ludovic Courtès
2017-05-12 16:20 ` Alex Sassmannshausen
2017-05-12 21:28 ` Hartmut Goebel
2017-05-13 5:38 ` Unprivileged /gnu/store with PRoot - or relocate Pjotr Prins
2017-05-13 14:12 ` Ludovic Courtès [this message]
2017-05-13 7:04 ` Unprivileged /gnu/store with PRoot Maxim Cournoyer
2017-05-13 14:02 ` Ludovic Courtès
2017-06-08 15:29 ` Ricardo Wurmus
2017-06-09 8:09 ` Ludovic Courtès
2017-07-16 12:35 ` Pjotr Prins
2017-07-16 12:51 ` Pjotr Prins
2017-07-16 16:09 ` Pjotr Prins
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=8737c83kxu.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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.