unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: bbb ee <blasforr@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Tobias Geerinckx-Rice <me@tobias.gr>, help-guix@gnu.org
Subject: Re: guix shell: error: mount: Invalid argument
Date: Mon, 21 Nov 2022 23:45:28 +0100	[thread overview]
Message-ID: <CALNLCmXr9HJYNTCDiu2eecMf-=CGZg0sgeFVkM2v=mQ0MtT7tA@mail.gmail.com> (raw)
In-Reply-To: <CALNLCmV0yXntLO1q9nR0xTBjf2wcEhdesPwidhcC0sT35qCitw@mail.gmail.com>

I have submitted a bug report : https://issues.guix.gnu.org/issue/59425.
Tobias is right, some of my tests fail because the current path is a
mountpoint, but other tests fail because some paths of the host system
can't be mounted.

`guix shell --container coreutils -- echo Elmo` is runnable for me if I
avoid this two condition above

Le dim. 20 nov. 2022 à 10:32, bbb ee <blasforr@gmail.com> a écrit :

> I have posted in the help mailing list, because I want to be sure that the
> command doesn't run is not because of bad usage from me. Apparently, my
> usage is correct, it is from my environment.
>
> I will also post a bug report. But the difficulty to get help for this
> problem is to provide a reproducible test. I have tried to reproduce this
> issue in a guix container
> ```
> dev_1@dev_1 /mnt/recoverData$ guix shell --no-cwd --network --container
> guix
> dev_1@dev_1 ~ [env]$ guix-daemon &
> dev_1@dev_1 ~ [env]$ guix shell --container coreutils -- echo Elmo
> accepted connection from pid 3, user dev_1
> substitute: guix substitute: warning: ACL for archive imports seems to be
> uninitialized, substitutes may be unavailable
> ..
> ```
> The issue with my reproducible test is that the guix in guix container
> doesn't find any substitute, so it will compile all package, which will
> take time.
>
>
> Le dim. 20 nov. 2022 à 01:29, Maxim Cournoyer <maxim.cournoyer@gmail.com>
> a écrit :
>
>> Hi,
>>
>> Tobias Geerinckx-Rice <me@tobias.gr> writes:
>>
>>
>> [...]
>>
>> > ~ λ guix shell -C --expose=/proc=/test coreutils -- echo Elmo
>> > world
>> > guix shell: error: mount: mount "/proc" on
>> > "/tmp/guix-directory.zTa1qb//test": Invalid argument
>> >
>> >
>> > Weird!  Clearly, /proc is imbued with magical Kernel magick and
>> > simply canno— what?  Oh:
>> >
>> > ~ λ mount | grep /proc
>> > none on /proc type proc (rw,relatime)
>> > binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc
>> > (rw,relatime)
>> >
>> >
>> > Surely not…
>> >
>> > ~ λ sudo umount /proc/sys/fs/binfmt_misc
>> >
>> > ~ λ guix shell -C --expose=/proc=/test coreutils -- echo Elmo
>> > world
>> > Elmo world
>> >
>> > …huh.
>> >
>> > So, ‘guix shell --container’ apparently takes issue with rbind'ing
>> > mounts, or something like that.
>> >
>> > Maybe that's something Guix can handle by bind-mounting the entire
>> > subtree itself, or maybe it's a hard permissions error enforced by
>> > the kernel.  I don't know.
>> >
>> > Someone with podman/Docker/similar experience might.
>>
>> I'm not useful, but just want to point out that this looks a lot like
>> https://issues.guix.gnu.org/46782 (guix environment --expose options
>> cannot be layered onto $PWD).
>>
>> --
>> Thanks,
>> Maxim
>>
>

      reply	other threads:[~2022-11-21 23:08 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
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 [this message]

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='CALNLCmXr9HJYNTCDiu2eecMf-=CGZg0sgeFVkM2v=mQ0MtT7tA@mail.gmail.com' \
    --to=blasforr@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --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).