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

From: Josef Bacik

Date: Thu Nov 19 2026 - 12:31:09 EST


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.

> 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.

> both of you: Can we please make it possible to do the parts of this
> that oughtn't require privilege without privilege?

Agreed, we need to come up with a design for this.

Thanks,

Josef