Re: [RFC PATCH v2 00/13] Namespace for namespace roots

From: Jarkko Sakkinen

Date: Wed Nov 18 2026 - 12:08:45 EST


On Wed, Nov 18, 2026 at 07:04:21PM +0200, Jarkko Sakkinen wrote:
> On Wed, Nov 18, 2026 at 08:59:39AM -0800, Andy Lutomirski wrote:
> > On Tue, Nov 17, 2026 at 3:14 PM Jarkko Sakkinen <jarkko@xxxxxxxxxx> wrote:
> > >
> > > OVERVIEW
> > > ========
> > >
> > > A root namespace (rootns) is a kernel object backed by a file descriptor
> > > that binds together:
> > >
> > > 1. A full or partial set of detached namespaces.
> > > 2. A dedicated PID namespace for spawning processes into, signaling
> > > members, and polling or waiting on PID 1 exit.
> > > 3. An initially empty mount namespace (CLONE_EMPTY_MNTNS) that must be
> > > populated before going live, without inheriting host mount-tree
> > > ancestors.
> > >
> > > Work on this feature started in 2025 from David Howells' container object
> > > patch set [1], which I turned into a namespace for namespace roots and
> > > rebuilt around that premise.
> > >
> > > While the patch set is manually written, the original motivation came
> > > from isolating LLM agents. Running untrusted agent workloads made it
> > > clear that OCI runtimes need to minimize their live configuration
> > > surface.
> > >
> > > Assembling mounts, credentials, and namespaces inside helper processes
> > > with a half-configured container is what I see as the main challenge,
> > > and the existential debate around namespaces and container objects is an
> > > unfocused discussion topic.
> >
> >
> > I've skimmed some of the series, and I see a bunch of good ideas that
> > involve using an fd to manage a thing. But I'm wondering how much of
> > the value is added by that and how much is added by having a new
> > *type* of thing: the "rootns".
> >
> > How much of the value comes from the rootns vs the new APIs to
> > configure namespaces without entering them first?
> >
> > For that matter, the cells series also seems to contain a (possibly
> > very similar) variant of the same thing.
> >
> > Would it make sense to come up with a patchset that does *just* the
> > configure-a-namespace-by-fd part? It seems to me that this should be
> > an easier thing to agree on, and it's a big part of the complexity of
> > all of this, and it solves a real problem even without
> > cells/rootnses/jails/whatever.
>
> Is it more accurately scope the part that is "just the fd-part" and
> what you consider as "extra cruft"?
>
> I.e., where do you draw the border?

I'm asking this because I had similar thoughts when I started this back
in 2025. David had some good ideas but it did more than having a fd
that does not go live before everything is set up properly.

Then I thought that, I guess people who proactively on the topic do
something more lean and compact, and never sent roonts patches.
I'm not seeing anything more lean and compact.

>
> >
> > --Andy
>
> Br, Jarkko

Br, Jarkko