From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: "Etienne B. Roesch" <etienne.roesch@gmail.com>
Cc: Felix Lechner <felix.lechner@lease-up.com>, <help-guix@gnu.org>,
<guix-science@gnu.org>
Subject: Re: [ext] Re: guix on nfs based systems
Date: Thu, 14 Dec 2023 20:35:25 +0100 [thread overview]
Message-ID: <874jgk8t91.fsf@mdc-berlin.de> (raw)
In-Reply-To: <CAPX-MzBchrjepXk3haNaUPUpxiXfMf3gcvsE_mRnAjdrthEUog@mail.gmail.com>
Hi Etienne,
> I think we've arrived at the limit of how I understand the daemon to work, and GUIX_DAEMON_SOCKET. I think I understand that you
> are using a single node (hpc of sort I imagine), where users create sessions, and within which you provide the guix command, having
> set up GUIX_DAEMON_SOCKET to a unix-domain socket (to that same node / itself). That makes total sense in the context of the single
> node. Did I get that right?
No, we provide Guix on *all* cluster nodes and workstations, but they
all talk to a single guix-daemon, which is the sole manager of /gnu. We
provide a default Guix for all those who haven’t yet run “guix pull” at
/gnu/remote/bin/guix. That location is on the PATH on all machines.
This script does three things:
- it sets GUIX_DAEMON_SOCKET to http://guix-node:9999
- it removes “gc” from the arguments and prints a warning (this is not
enough to prevent GC, but it works well enough)
- it looks for the user’s “guix” in /home/who/.config/guix/current/bin;
if it exists it execs that “guix” with the arguments; otherwise it
executes the shared default Guix.
> The issue with profiles you are mentioning is interesting; I haven't
> quite thought it through yet. I think I would personally want users to
> be able to create profiles (for reproducibility reasons) but I guess
> it would work the same way with guix shells built from manifests,
> maybe slightly less easy to interact with, I don't know.
In my experience, profiles always end up growing in a stateful manner.
People use them to satisfy old habits of installing, removing, and
upgrading packages, and inevitably they run into conflicts because they
install new packages to a profile built with an older version of Guix.
Yes, using manifests would avoid that, but if you’re already using
manifests you might as well use “guix shell -m”. For long-term
reproducibility we recommend recording the current channels with “guix
describe -f channels” and add the output to version control.
With “guix time-machine -C channels.scm -- shell -m manifest.scm” people
can restore the environment in the future.
--
Ricardo Wurmus
System administrator
BIMSB - Scientific Bioinformatics Platform
Max Delbrueck Center for Molecular Medicine
email: ricardo.wurmus@mdc-berlin.de
tel: +49 30 9406 1796
next prev parent reply other threads:[~2023-12-14 19:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPX-MzA5P1A8u8QbR-g-Lx4gONQ+o7mO1TZzhZ3UHh=KdUxhvw@mail.gmail.com>
2023-11-23 6:32 ` guix on nfs based systems Efraim Flashner
2023-11-23 9:41 ` Etienne B. Roesch
2023-11-26 7:33 ` Efraim Flashner
2023-12-14 14:41 ` Ricardo Wurmus
2023-11-23 13:03 ` Felix Lechner via
2023-11-23 13:03 ` Felix Lechner via Guix-Science
2023-11-24 18:08 ` Etienne B. Roesch
2023-11-26 7:36 ` Efraim Flashner
2023-12-13 10:17 ` Etienne B. Roesch
2023-12-14 14:46 ` Ricardo Wurmus
2023-12-14 15:28 ` Etienne B. Roesch
2023-12-14 15:33 ` Pierre-Antoine Bouttier
2023-12-14 15:33 ` Pierre-Antoine Bouttier
2023-12-14 15:57 ` Etienne B. Roesch
2023-12-14 19:35 ` Ricardo Wurmus [this message]
2024-02-15 16:14 ` Simon Tournier
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=874jgk8t91.fsf@mdc-berlin.de \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=etienne.roesch@gmail.com \
--cc=felix.lechner@lease-up.com \
--cc=guix-science@gnu.org \
--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.
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).