From: DJ Delorie <dj@redhat.com>
To: Michael Hudson-Doyle <michael.hudson@canonical.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] linux: return UNSUPPORTED in tst-mount if support_become_root fails
Date: Thu, 14 Jul 2022 19:16:31 -0400 [thread overview]
Message-ID: <xno7xrcmk0.fsf@greed.delorie.com> (raw)
In-Reply-To: <CAJ8wqteDe-VGVM56aPzYfzzpdUxULnN6wbzuWi0U+RUAQjUo7g@mail.gmail.com>
Michael Hudson-Doyle <michael.hudson@canonical.com> writes:
> All the test-container tests in Ubuntu builds end up UNSUPPORTED with
> test-container.c:1130: unable to unshare user/fs: Operation not permitted
> so that wouldn't really help here (I should probably look into why this is).
Yeah, Debian-based distros default to disabling user containers. There
should be a hint printed as to how to re-enable them, but that's on a
per-system basis, and up to the admin.
next prev parent reply other threads:[~2022-07-14 23:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 3:23 Michael Hudson-Doyle
2022-07-14 11:24 ` Adhemerval Zanella Netto
2022-07-14 19:03 ` Carlos O'Donell
2022-07-14 19:18 ` DJ Delorie
2022-07-14 22:50 ` Michael Hudson-Doyle
2022-07-14 23:16 ` DJ Delorie [this message]
2022-07-15 0:06 ` [PATCH v2] linux: return UNSUPPORTED in tst-mount if !support_can_chroot Michael Hudson-Doyle
2022-07-15 7:07 ` Florian Weimer
2022-07-15 15:35 ` Carlos O'Donell
2022-07-15 15:44 ` Florian Weimer
2022-07-17 21:44 ` Michael Hudson-Doyle
2022-07-15 21:01 ` Michael Hudson-Doyle
2022-07-16 0:26 ` Carlos O'Donell
2022-07-17 23:16 ` [PATCH v3] linux: return UNSUPPORTED from tst-mount if entering mount namespace fails Michael Hudson-Doyle
2022-07-18 12:59 ` Carlos O'Donell
2022-07-18 18:59 ` Michael Hudson-Doyle
2022-07-19 2:51 ` Carlos O'Donell
2022-07-18 13:13 ` Mark Wielaard
2022-07-18 13:45 ` Carlos O'Donell
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=xno7xrcmk0.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=michael.hudson@canonical.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.
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).