Dan Nicholson

I think that the admin builtin is applying the mount namespace too aggressively at https://github.com/ostreedev/ostree/blob/main/src/ostree/ot-main.c#L629. I'm going to do a quick test with that and see if I reproduce it...

I couldn't reproduce in an x86_64 VM where the `unshare` happens. I guess in ostree the mount propagation (at least on my system) is still shared and not private or...

Ok, I think that's why you're seeing this issue and not me. Your `/` is private whereas mine is shared. When a new mount namespace is created, the new overlay...

> I'm sorry but I know few about shared mount. Do you have any idea why my `/` is private while yours is shared? Is it related to a configuration...

Good to know you found a fix. I'm going to leave this open and retitle it since I believe that ostree should not be using a mount namespace in this...

Isn't that already the logic for sysroot cleanup, or are you basically describing #2510? Or do you mean you don't want the temporary ballooning to 3 deployments prior to rebooting...

Bikeshedding, but I think I'd expect the maximum deployments to be the non-ballooned value. The ballooned number of deployments is a temporary implementation detail. As a user it would bug...

Right, I thought of that while after I walked away. They're actually 2 orthogonal concepts to me. Specifying the maximum number of deployments allows you to say you want no...

Good points. I think if there are pinned deployments, they should just be ignored for the purposes of pruning deployments. For more than 2 non-pinned deployments, I think they should...

> I, personally, should not be the sole Debian maintainer of a library that depends on Rust, because I don't know Rust (I know I need to learn it, but...