From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
<richard.purdie@linuxfoundation.org>
Cc: "YP docs mailing list" <docs@lists.yoctoproject.org>
Subject: Re: [docs] Does Ubuntu 24.04 and newer still require AppArmor tweaking to run bitbake?
Date: Mon, 14 Sep 2026 10:31:42 +0200 [thread overview]
Message-ID: <DLEWE65BFU3W.A4IWZNKSX1NU@bootlin.com> (raw)
In-Reply-To: <e2e6840c-d972-d4d4-4c67-ba54cae6dce4@crashcourse.ca>
On Fri Sep 11, 2026 at 7:41 PM CEST, Robert P. J. Day wrote:
> On Fri, 11 Sep 2026, Richard Purdie via lists.yoctoproject.org wrote:
>
>> On Fri, 2026-09-11 at 05:16 -0400, Robert P. J. Day via
>> lists.yoctoproject.org wrote:
>> > On Fri, 11 Sep 2026, Antonin Godard via lists.yoctoproject.org wrote:
>> >
>> > > Hi,
>> > >
>> > > On Thu Sep 10, 2026 at 2:57 PM CEST, Robert P. J. Day wrote:
>> > > >
>> > > > I use stock Debian so I haven't needed to mess with this, but
>> > > > Ubuntu
>> > > > once had this issue with AppArmor:
>> > > >
>> > > > https://developerwiki.proventusnova.com/Error:_BitBake_+_AppArmor_User_Namespace_Restriction_Fix
>> > > >
>> > > > If that's still a problem, it doesn't seem to be mentioned in the
>> > > > docs.
>> > >
>> > > I don't have a running Ubuntu 26.04 distribution but I would say it
>> > > is still the
>> > > case if 26.04 is still running AppArmor.
>> > >
>> > > Users will face the same error as before which is:
>> > >
>> > > bb.fatal("User namespaces are not usable by BitBake, possibly due
>> > > to AppArmor.\n"
>> > > "See
>> > > https://discourse.ubuntu.com/t/ubuntu-24-04-lts-noble-numbat-release-notes/39890#unprivileged-user-namespace-restrictions
>> > > for more information.")
>> > >
>> > > In OE-Core's meta/lib/oe/sanity.py.
>> > >
>> > > This sounds like something we could say in the docs. Would you mind
>> > > sending a
>> > > patch for that?
>> >
>> > seems to me that the proper place for this would be a "warning"
>> > admonition at the tail end of this section:
>> >
>> > https://docs.yoctoproject.org/ref-manual/system-requirements.html#supported-linux-distributions
>> >
>> > i wouldn't want to get into incredible detail there, just point out
>> > that starting with ubuntu 24.04, you would get that namespaces error,
>> > then refer the reader to that discourse link for the solution. does
>> > that sound adequate? i don't think the YP docs need to reproduce the
>> > solution in its entirety.
>>
>> This is important enough I think we should have it documented
>> ourselves, not externally where it could disappear.
>
> So where should it go, and is anyone else keen on doing it? :-)
I think it should go under the "Ubuntu and Debian" section in a "warning"
admonition, as you suggested:
https://docs.yoctoproject.org/ref-manual/system-requirements.html#ubuntu-and-debian
Thanks!
Antonin
prev parent reply other threads:[~2026-09-14 8:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 12:57 Does Ubuntu 24.04 and newer still require AppArmor tweaking to run bitbake? Robert P. J. Day
2026-09-11 7:36 ` [docs] " Antonin Godard
2026-09-11 8:11 ` Richard Purdie
2026-09-11 9:16 ` Robert P. J. Day
2026-09-11 13:46 ` Richard Purdie
2026-09-11 17:41 ` Robert P. J. Day
2026-09-14 8:31 ` Antonin Godard [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DLEWE65BFU3W.A4IWZNKSX1NU@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=rpjday@crashcourse.ca \
/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