From: bbb ee <blasforr@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix@gnu.org
Subject: Re: guix shell: error: mount: Invalid argument
Date: Sat, 19 Nov 2022 21:18:47 +0100 [thread overview]
Message-ID: <CALNLCmUXVGXpMem-ZhKMm9yLBkXMCOx_JLGXZ=w90O3bGp7FLA@mail.gmail.com> (raw)
In-Reply-To: <87ilja3eoz.fsf@nckx>
> Does this system have ‘uncommon’ kernel restrictions in place,
like SELinux or other hardening?
No, I have never used this feature.
> Is there anything printed in dmesg when the container fails to start?
No changement in dmesg
Le sam. 19 nov. 2022 à 20:50, Tobias Geerinckx-Rice <me@tobias.gr> a écrit :
> 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
>
next prev parent reply other threads:[~2022-11-19 20:19 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
2022-11-19 20:18 ` bbb ee [this message]
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
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='CALNLCmUXVGXpMem-ZhKMm9yLBkXMCOx_JLGXZ=w90O3bGp7FLA@mail.gmail.com' \
--to=blasforr@gmail.com \
--cc=help-guix@gnu.org \
--cc=me@tobias.gr \
/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).