All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: overlayfs <linux-unionfs@vger.kernel.org>,
	StuartIanNaylor <rolyantrauts@gmail.com>,
	Linux Containers <containers@lists.linux-foundation.org>,
	kmxz <kxzkxz7139@gmail.com>, "zhangyi (F)" <yi.zhang@huawei.com>,
	Miklos Szeredi <miklos@szeredi.hu>,
	Christian Brauner <christian.brauner@ubuntu.com>
Subject: Re: OverlaysFS offline tools
Date: Fri, 5 Jun 2020 17:38:40 +0300	[thread overview]
Message-ID: <CAOQ4uxhP0VPMUSrPReKVaWLzyGkr1CFqiWNtGWOA29uLb0NEhg@mail.gmail.com> (raw)
In-Reply-To: <20200605143217.GB123988@redhat.com>

> Hi Amir,
>
> I can't seem to access this abstract proposal (Despite the fact I
> created a new login id).
>

Maybe it needs to be accepted to become public, anyway:

Containers are by far the biggest use case for overlayfs.
Yet, there seems to be very little cross talk between overlayfs and
containers mailing lists.

This talk is going to present some opt-in overlayfs features that were
added in recent years (redirect_dir, index, nfs_export, xino,
metacopy).

Most of those features have not been enabled by most container
runtimes, because of various reasons:

* Requires more development in userspace (image migration)
* Unrelated runtime bugs (mount leaks)
* Mismatch for containers needs
* Lack of promotion

This talk is about giving the opportunity to container runtime
developers to better understand what they may get from overlayfs.

This talk is not about containers wish list from overlayfs, because
userns overlayfs mount needs 45 minutes on its own...

Thanks,
Amir.

  reply	other threads:[~2020-06-05 14:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-08  7:27 OverlaysFS offline tools Amir Goldstein
2020-01-08 14:06 ` Vivek Goyal
2020-01-08 15:29   ` Tycho Andersen
2020-01-13 15:28   ` Daniel Walsh
2020-01-13 18:02     ` Amir Goldstein
2020-01-13 20:07     ` Christian Brauner
2020-06-05  5:33   ` Amir Goldstein
2020-06-05 14:32     ` Vivek Goyal
2020-06-05 14:38       ` Amir Goldstein [this message]
2020-06-05 15:19         ` Christian Brauner
2020-06-05 15:13     ` Christian Brauner
2020-08-11  9:57     ` Amir Goldstein

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=CAOQ4uxhP0VPMUSrPReKVaWLzyGkr1CFqiWNtGWOA29uLb0NEhg@mail.gmail.com \
    --to=amir73il@gmail.com \
    --cc=christian.brauner@ubuntu.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=kxzkxz7139@gmail.com \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=rolyantrauts@gmail.com \
    --cc=vgoyal@redhat.com \
    --cc=yi.zhang@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.