From: Tobias Geerinckx-Rice <me@tobias.gr>
To: bbb ee <blasforr@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: guix shell: error: mount: Invalid argument
Date: Sat, 19 Nov 2022 20:46:43 +0100 [thread overview]
Message-ID: <87ilja3eoz.fsf@nckx> (raw)
In-Reply-To: <CALNLCmUZn5_sYiT1NYMvFX9bwTOV1HGX1dfZZzsyUQ37XwDt4Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
bbb ee 写道:
>> So /home/dev_1 (not $HOME; see error message)
No, I was confused as well, sorry.
In the back of my mind was another user reporting they used some
FUSE-based encryption of $HOME, and I thought you might be using
that. This tainted my thinking.
I have no other idea what could be happening. What I ‘reproduced’
in my previous mail is probably not what is happening to you, even
if the error messages are the same.
But it is definitely something related to your installation:
> guix shell --container coreutils -- echo Elmo
should, of course, always work.
Does this system have ‘uncommon’ kernel restrictions in place,
like SELinux or other hardening? Is there anything printed in
dmesg when the container fails to start?
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2022-11-19 19:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 11:15 guix shell: error: mount: Invalid argument bbb ee
2022-11-19 11:23 ` Tobias Geerinckx-Rice
2022-11-19 19:17 ` bbb ee
2022-11-19 19:21 ` Tobias Geerinckx-Rice
2022-11-19 19:27 ` bbb ee
2022-11-19 19:46 ` Tobias Geerinckx-Rice [this message]
2022-11-19 20:18 ` bbb ee
2022-11-19 20:19 ` Tobias Geerinckx-Rice
2022-11-19 20:20 ` bbb ee
2022-11-20 0:29 ` Maxim Cournoyer
2022-11-20 9:32 ` bbb ee
2022-11-21 22:45 ` bbb ee
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=87ilja3eoz.fsf@nckx \
--to=me@tobias.gr \
--cc=blasforr@gmail.com \
--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.