All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: rpjday@crashcourse.ca, antonin.godard@bootlin.com
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: Fri, 11 Sep 2026 14:46:13 +0100	[thread overview]
Message-ID: <a1ade29f24430238de77852ca5a8045e774a7d75.camel@linuxfoundation.org> (raw)
In-Reply-To: <f983a674-d30d-7659-45f8-ac32a1187c41@crashcourse.ca>

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.

Cheers,

Richard


  reply	other threads:[~2026-09-11 13:46 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 [this message]
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=a1ade29f24430238de77852ca5a8045e774a7d75.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.