archive mirror
 help / color / mirror / Atom feed
From: Vivek Goyal <>
To: Amir Goldstein <>
Cc: Zhihao Cheng <>,
	Miklos Szeredi <>,
	overlayfs <>,
	Daniel J Walsh <>,
	Nalin Dahyabhai <>
Subject: Re: [QUESTION] Why overlayfs cannot mounted as nfs_export and metacopy?
Date: Tue, 10 Aug 2021 16:00:17 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, Aug 10, 2021 at 03:48:55PM -0400, Vivek Goyal wrote:

> > But beyond the complexity, what is the benefit?
> > I was under the impression that container manager do not know how
> > to build images with metacopy, so what are the chances of actually
> > seeing metacopy in middle layers in the wild?
> Sure, we don't put metacopy inodes into portable images. But I thougt
> this could be part of a lower directory on same system. For example,
> docker devicemapper driver used to take an image and explode that
> on a thin volume. Then it will take a snaphost, modify some files
> and prefix that intermediate state with "-init". And then containers
> will use this "-init" as base for container rootfs and take snapshot
> of this.
> I am not sure if container managers are doing this for overlayfs
> or not on same system. But I will not be surprised if somebody
> decides to do that. That's is change some metadata in image
> (which triggers metacopy) and then use upper layer as lower layer
> for container rootfs.

In the past we were experimenting with chowning all files in image
according to user namespace of container using metacopy and use chowned
dir as lower layer for container rootfs. Ofcourse now, idmapped mounts
are available (not sure if it works with overlayfs yet or not) so chowning
images should not be required.

But point I am trying to make it is that I will not be surprised
that somebody comes up with use case of metacopy inode in lower
layer. So will be nice we take care of that configuration as well
while enabling metacopy with nfs_export (and deal with extra


  reply	other threads:[~2021-08-10 20:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-07 10:17 [QUESTION] Why overlayfs cannot mounted as nfs_export and metacopy? Zhihao Cheng
2021-08-07 11:05 ` Amir Goldstein
2021-08-07 16:37   ` Amir Goldstein
2021-08-09  9:21     ` Zhihao Cheng
2021-08-09 21:35     ` Vivek Goyal
2021-08-10  4:17       ` Amir Goldstein
2021-08-10 19:48         ` Vivek Goyal
2021-08-10 20:00           ` Vivek Goyal [this message]
2021-08-11  6:51           ` Amir Goldstein
2021-08-16 18:27             ` Vivek Goyal
2021-08-16 18:44               ` Amir Goldstein
2021-08-16 19:00                 ` Vivek Goyal
2021-08-09 19:56   ` Vivek Goyal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).