From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com ([209.132.183.28]:46320 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387456AbfFJSko (ORCPT ); Mon, 10 Jun 2019 14:40:44 -0400 Date: Mon, 10 Jun 2019 14:40:43 -0400 From: Vivek Goyal Subject: Re: [PATCH v2] overlay: allow config override of metacopy/redirect defaults Message-ID: <20190610184043.GD25290@redhat.com> References: <20190607010431.11868-1-mcoffin13@gmail.com> <20190607205105.21858-1-mcoffin13@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-unionfs-owner@vger.kernel.org To: Miklos Szeredi Cc: Amir Goldstein , Matt Coffin , overlayfs , Daniel J Walsh List-ID: On Sun, Jun 09, 2019 at 09:14:38PM +0200, Miklos Szeredi wrote: > On Sat, Jun 8, 2019 at 8:47 PM Amir Goldstein 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. Thanks Vivek