From: "Ludovic Courtès" <ludo@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 35662@debbugs.gnu.org
Subject: bug#35662: Really relocatable binaries crash with Permission denied
Date: Tue, 14 May 2019 22:43:56 +0200 [thread overview]
Message-ID: <87h89wydf7.fsf@gnu.org> (raw)
In-Reply-To: <20190514080525.xspgsob6payn2ioa@pelzflorian.localdomain> (pelzflorian@pelzflorian.de's message of "Tue, 14 May 2019 10:05:25 +0200")
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
> On Mon, May 13, 2019 at 10:45:24PM +0200, pelzflorian (Florian Pelz) wrote:
>> On Mon, May 13, 2019 at 10:39:21PM +0200, Ludovic Courtès wrote:
>> > I suspect ZFS-on-Linux (right?) is doing something unusual here:
>>
>> I suppose it is ZFS on Linux; it is Linux, I can ask the admins if it
>> could be something else.
>>
>
> The admins have confirmed that they use “Proxmox on ZFS” (judging from
> <https://pve.proxmox.com/wiki/ZFS_on_Linux> it is ZFS on Linux) and
> they have confirmed that they have disabled user namespaces in their
> Proxmox settings.
User namespaces are orthogonal to file systems, but anyway it looks like
ZFS is refusing to let us do these things.
I don’t have any great option to offer. You could perhaps modify
run-in-namespace.c so that it doesn’t even try user namespaces and
instead goes directly to the PRoot option?
However working around this behavior of ZFS it not completely trivial
and I’m not sure we should put much energy to paper over non-standard
file system behavior.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2019-05-14 20:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 22:01 bug#35662: Really relocatable binaries crash with Permission denied pelzflorian (Florian Pelz)
2019-05-10 5:54 ` pelzflorian (Florian Pelz)
2019-05-10 21:50 ` Ludovic Courtès
2019-05-11 5:05 ` pelzflorian (Florian Pelz)
2019-05-13 7:49 ` Ludovic Courtès
2019-05-13 10:34 ` pelzflorian (Florian Pelz)
2019-05-13 13:54 ` Ludovic Courtès
2019-05-13 15:17 ` pelzflorian (Florian Pelz)
2019-05-13 20:39 ` Ludovic Courtès
2019-05-13 20:45 ` pelzflorian (Florian Pelz)
2019-05-14 8:05 ` pelzflorian (Florian Pelz)
2019-05-14 20:43 ` Ludovic Courtès [this message]
2019-05-14 21:04 ` pelzflorian (Florian Pelz)
2019-05-15 16:15 ` Ludovic Courtès
2019-05-15 15:20 ` Giovanni Biscuolo
2019-05-16 11:02 ` pelzflorian (Florian Pelz)
2019-05-16 11:10 ` 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
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=87h89wydf7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=35662@debbugs.gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).