On Tue, May 20, 2025 at 06:40:35PM +0200, Miklos Szeredi wrote: > On Tue, 20 May 2025 at 17:21, Kent Overstreet <kent.overstr...@linux.dev> > wrote: > > > Docker mounts the image, but then everything explodes when you try to > > use it with what look to the user like impenetrable IO errors. > > > > That's a bad day for someone, or more likely a lot of someones. > > Wouldn't it be docker's responsibility to know that that won't work > with overlayfs?
Why would it be? > Any error, whether at startup or during operation is not something the > user will like. > > What am I missing? A _mount_ error due to misconfiguration is expected operation, and we've built mechanisms for reporting those errors in a way that users can understand what's going on. That's not true for normal file accesses post mount.
