On Mon, Jun 10, 2019 at 02:40:43PM -0400, Vivek Goyal wrote: > On Sun, Jun 09, 2019 at 09:14:38PM +0200, Miklos Szeredi wrote: > > On Sat, Jun 8, 2019 at 8:47 PM Amir Goldstein <amir73il@xxxxxxxxx> wrote: > > > > > And then every time that a feature needs to be turned off for some reason > > > that also needs to be taken into account. > > > IOW, I advise against diving into this mess. You have been warned ;-) > > > > Also a much more productive direction would be to optimize building > > the docker image based on the specific format used by overlayfs for > > readirect_dir/metacopy. > > > > To me it seems like a no-brainer, but I don't know much about docker, so... > > [ cc Daniel Walsh] > > Hi Miklos, > > Can you elaborate a bit more on what docker/container-storoage and do > here to expedite image generation with redirect_dir/metacopy enabled. > > They can't pack these xattrs in image because image will not be portable. > It will be overlayfs specific and can't be made to work on target without > overlayfs. Are you referring to apps being able to traverse lower layers and do the redirect_dir and metacopy resoltion as kernel does. To me that process is not trivial. Having a library might help with adoption though. Vivek
