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

From: Andy Lutomirski

Date: Thu Nov 19 2026 - 18:27:33 EST


On Thu, Nov 19, 2026 at 2:50 PM Andy Lutomirski <luto@xxxxxxxxxxxxxx> wrote:
>
> On Thu, Nov 19, 2026 at 9:30 AM Josef Bacik <josef@xxxxxxxxxxxxxx> wrote:
> >
> > On Wed, Nov 18, 2026 at 9:46 AM Andy Lutomirski <luto@xxxxxxxxxxxxxx> wrote:
> > > cells: The dance where I create an anonymous mountns, mount stuff into
> > > it, and then attach it to the cell is cute. But I think the userns
> > > interaction is wrong: you are making me assemble all the mounts in
> > > *my* userns and then clone the entire tree into a fresh, non-anonymous
> > > mountns bound to the current userns. And that clone operation is not
> > > free and serves no actual practical purpose.
> >
> > The copy buys us nothing, agreed. That's just what the mount API gives
> > me to work with today, it's not something cells wants. If I could make
> > an empty mount namespace and fill it by fd I'd use that, the "root" slot
> > takes a mount namespace fd already. Extending the API for that makes
> > sense to me on its own.
> >
> > The mount namespace staying with the builder's userns is on purpose
> > though, that's what keeps the cell from mounting anything no matter what
> > capabilities it was given. The builder sets the tree up and hands it
> > over, so the cell only ever has what it was given, and the mount code
> > isn't something it can attack from the inside.
>
> I don't get it.
>
> Using the builder's user namespace means that the contained processes
> can't be ns_capable on mntns->userns. But this solves very few
> problems unless you also deny the contained processes the ability to
> unshare userns and make a new mountns, and if you can do that, surely
> you can also deny the ability to modify the mount namespace.
>
> As just one example, a mount namespace could have a little flag to say
> that it's *in* one userns but its owner is a different userns.
>
> >
> > > cells: I find it *incredibly annoying* that one generally cannot put
> > > new mounts into an existing container using most existing container
> > > managers. I hit this on a surprisingly regular basis. You seem to be
> > > baking this into the whole cells design. Why?
> >
> > By design. Allowing changes to a running container is what causes the
> > problems. If you need another mount, tear it down and build it again.
>
> What problems?

I'll add:

On a non-container Linux system, you can hot-add a removable drive.
On a Linux-hosted VM, you can hot-add all kinds of devices, with or
without the help of the hypervisor. (The hypervisor can hot-add a
device, and the guest can mount network devices or newly added USB
devices on a port that was already assigned, etc.)

For some reason, on Docker and its sort-of-clones, approximately the
best you can do is rbind in a directory and then mount things into
that directory from outside. This is sad.

I get that there are plenty of workloads for which this limitation is
reasonable, and there are more workloads for which this limitation is
silly and people have learned to live with it because everyone
imitates Docker and Docker is limited. But there are also workloads
that I hit on a surprisingly regular basis for which this limitation
is genuinely annoying.

If you want to write a container manager that shares the same
limitation, fine. But please don't make it into the kernel without a
compelling reason.

(I personally think that Docker has a *lot* of weird properties that
make little sense. This is just one of them.)