all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Felix Lechner via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 58640@debbugs.gnu.org
Subject: bug#58640: Garbage collector ('gc') deletes valid user roots when $HOME is inaccessible
Date: Wed, 19 Oct 2022 10:14:05 -0700	[thread overview]
Message-ID: <CAFHYt57EhbFK1c+V9Kw7k-_zkiSRkLwmoYawdRcuiA9L-EOXvg@mail.gmail.com> (raw)

Hi,

The Guix garbage collector ('gc') deletes valid user roots when those
links are not resolvable via the user's home folder in places such as

    ~/.cache/guix/profiles/

which potentially leaves the user without a working profile.

Home folders are not always accessible to the root user, and may
therefore also not be accessible to the Guix daemon.  In some
networked setups, for example, home folders can be automounted.

In my particular case, the home folder was inaccessible due to my
encrypted filesystem's security policies, which are enforced by FUSE
when using gocryptfs. [1]

The FUSE feature can be turned off [2] and Gocryptfs can 'allow_other'
[3] but that is a large concession and may not solve the daemon's
alleged (mis-)behavior in the general case.

Thank you for reading!

Kind regards
Felix Lechner

[1] https://nuetzlich.net/gocryptfs/
[2] https://unix.stackexchange.com/a/17423
[3] https://manpages.debian.org/bullseye/gocryptfs/gocryptfs.1.en.html




             reply	other threads:[~2022-10-19 17:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 17:14 Felix Lechner via Bug reports for GNU Guix [this message]
2022-10-20 11:41 ` bug#58640: Garbage collector ('gc') deletes valid user roots when $HOME is inaccessible Liliana Marie Prikler
2022-10-21  7:30 ` Ludovic Courtès

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=CAFHYt57EhbFK1c+V9Kw7k-_zkiSRkLwmoYawdRcuiA9L-EOXvg@mail.gmail.com \
    --to=bug-guix@gnu.org \
    --cc=58640@debbugs.gnu.org \
    --cc=felix.lechner@lease-up.com \
    /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.