On Fri, Jun 09, 2023 at 08:20:30AM -0400, Colin Walters wrote: > > > On Fri, Jun 9, 2023, at 7:45 AM, Christian Brauner wrote: > > > > Because the series you sent here touches on a lot of things in terms of > > infrastructure alone. That work could very well be rather interesting > > independent of PuzzleFS. We might just want to get enough infrastructure > > to start porting a tiny existing fs (binderfs or something similar > > small) to Rust to see how feasible this is and to wet our appetite for > > bigger changes such as accepting a new filesystem driver completely > > written in Rust. > > (Not a kernel developer, but this argument makes sense to me) > > > But aside from the infrastructure discussion: > > > > This is yet another filesystem for solving the container image problem > > in the kernel with the addition of yet another filesystem. We just went > > through this excercise with another filesystem. So I'd expect some > > reluctance here. Tbh, the container world keeps sending us filesystems > > at an alarming rate. That's two within a few months and that leaves a > > rather disorganized impression. > > I am sure you are aware there's not some "container world" > monoculture, there are many organizations, people and companies here That submission here explicitly references OCI v2. Composefs explicitly advertises 100% compatibility with OCI. So, there's a set of OCI specs including runtime and image. As far as I'm concerned you're all one container world under the OCI umbrella. We're not going to push multiple filesystems into the kernel that all do slightly different things but all serve the OCI container world and use some spec as an argument to move stuff into the kernel. The OCI initiative is hailed as unifying the container ecosystem. Hence, we can expect coordination.
