From: Ben Woodcroft <b.woodcroft@uq.edu.au>
To: help-guix <help-guix@gnu.org>
Subject: Non-privileged daemons and offloading
Date: Sun, 19 Jun 2016 23:07:38 +1000 [thread overview]
Message-ID: <5766991A.1020505@uq.edu.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 994 bytes --]
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 the daemon normally as a regular user, but I'm afraid of the
issues that arise due to inability to chroot as described in the manual.
Instead, I'm considering offloading the builds to a separate machine,
where a guix-daemon runs as sudo and so can run builds in the chroot.
IIUC, this gets around the issue of impurities in builds while not
requiring sudo.
One hole the plan I can see is that at least according to the manual,
offloads are defined in "/etc/guix/machines.scm" which as a regular user
I cannot modify. Is there any other way to specify offload machines e.g.
via an argument to 'guix-daemon'? Is there any better ways to go about
this whole thing in general?
Thanks,
ben
[-- Attachment #2: Type: text/html, Size: 1285 bytes --]
next reply other threads:[~2016-06-19 13:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-19 13:07 Ben Woodcroft [this message]
2016-06-20 8:05 ` Non-privileged daemons and offloading Ludovic Courtès
2016-06-20 12:23 ` Ludovic Courtès
2016-06-20 12:44 ` Thompson, David
2016-06-20 9:06 ` Roel Janssen
2016-07-30 4:11 ` Ben Woodcroft
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=5766991A.1020505@uq.edu.au \
--to=b.woodcroft@uq.edu.au \
--cc=help-guix@gnu.org \
/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.