unofficial mirror of guix-science@gnu.org 
 help / color / mirror / Atom feed
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: guix on nfs based systems
Date: Thu, 14 Dec 2023 15:46:01 +0100	[thread overview]
Message-ID: <87plz8alhc.fsf@mdc-berlin.de> (raw)
In-Reply-To: <CAPX-MzC+UnkD0K-kHj4JkRQ3FJj2dVRJO0DekvSuZdCgJbfi8g@mail.gmail.com>


"Etienne B. Roesch" <etienne.roesch@gmail.com> writes:

> Hiccups: we provide home dirs as nfs drives through the network. Using guix, we are thinking of creating one nfs drive, shared by all
> users, to contain /var/guix and /gnu/store, symlinked from /.
> As I understand, that should work, until a user decides to run "guix gc" (which would clear wrongly assumed unused profiles) or maybe
> until a user decides to launch several vms (which is theoretically possible, but doesn't happen often).

I would strongly discourage the use of profiles in users’ home
directories.  When introducing Guix we now only demo “guix shell”, which
is preferrable in most cases.  “guix gc” is problematic when profile
links are in locations that the daemon cannot read. 

> Efraim suggested using a shared daemon ssh-ing GUIX_DAEMON_SOCKET. We
> would probably run this on a separate vm. We are however unsure how it
> would behave when /var/guix/daemon-socket/socket is itself on an nfs.

We only export /var/guix/profiles, not anything else in /var/guix.
Using GUIX_DAEMON_SOCKET with a network port (make “guix-daemon” listen
on that port) is all we ever needed.

-- 
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


  reply	other threads:[~2023-12-14 14:48 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 [this message]
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               ` [ext] " Ricardo Wurmus
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=87plz8alhc.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).