From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
"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: Fri, 11 Sep 2026 09:36:49 +0200 [thread overview]
Message-ID: <DLCBCIBSXUHT.2SR3V23FN8VPD@bootlin.com> (raw)
In-Reply-To: <ec2658dc-005e-f6cc-d64e-0a1c15e992a7@crashcourse.ca>
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?
Thanks,
Antonin
next prev parent reply other threads:[~2026-09-11 7:37 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 ` Antonin Godard [this message]
2026-09-11 8:11 ` [docs] " 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
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=DLCBCIBSXUHT.2SR3V23FN8VPD@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.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