Hi,
Thanks all for the informative responses.
On 20/06/16 18:05, Ludovic Courtès wrote:
Hello!
What you describe here is a hot topic and definitely a commonly
requested feature. The difficulty here is that we’re hitting
limitations of the kernel, which requires root privileges to set up a
chr
On Mon, Jun 20, 2016 at 4:05 AM, Ludovic Courtès wrote:
> The Nix daemon recently switch to user namespaces:
>
> https://github.com/NixOS/nix/commit/c68e5913c71badc89ff346d1c6948517ba720c93
>
> We could backport this. However, running builds with UID 0 is
> potentially disruptive: some packages
l...@gnu.org (Ludovic Courtès) skribis:
> Regardless, it remains our best hope to support unprivileged daemons.
Also, I did not explicitly mention it, but I think this unprivileged
user namespace thing should just be one part of the strategy.
In parallel, it’s worth discussing with cluster sysad
Hello Ben,
It seems like we are facing a similar problem. A proper solution takes
a lot more work and a lot more time I believe. I am also currently
working on a more complete guide to do this, but here I tried to get the
essentials written down.
As far as software deployment goes, I have done
Hello!
What you describe here is a hot topic and definitely a commonly
requested feature. The difficulty here is that we’re hitting
limitations of the kernel, which requires root privileges to set up a
chroot and so on.
The way around it is Linux’ unprivileged “user namespaces”, as used by
‘guix
Hi there,
I've recently gotten access to a supercomputer where I don't have sudo,
and I'm trying to hatch a plan to run guix packaged programs.
Unfortunately, I don't have anything substantial like a container-based
build environment to add here, only a potential workaround idea.
I could run
