From: Christian Brauner <email@example.com>
To: Amir Goldstein <firstname.lastname@example.org>
Cc: Stephane Graber <email@example.com>,
Miklos Szeredi <firstname.lastname@example.org>,
LSM List <email@example.com>,
"zhangyi (F)" <firstname.lastname@example.org>
Subject: Re: Overlayfs @ Containers and checkpoint/restart micro-conference at LPC2018
Date: Sun, 9 Sep 2018 11:18:54 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4628 bytes --]
On Sun, Sep 09, 2018 at 09:31:02AM +0300, Amir Goldstein wrote:
> On Sun, Sep 9, 2018 at 4:31 AM Christian Brauner <firstname.lastname@example.org> wrote:
> > > [cc: overlayfs developers]
> > >
> > > Hi Stéphane!
> > Hey Amir,
> > I'm one of the co-organizers of the microconf.
> > >
> > > I am not planing to travel to LPC this year, so this is more of an FYI than
> > > a CFP, but maybe another overlayfs developer can pick up this glove??
> > Sure, that would be great.
> > >
> > > For the past two years I have participated in the effort to fix overlayfs
> > > "non-standard" behavior:
> > > https://github.com/amir73il/overlayfs/wiki/Overlayfs-non-standard-behavior
> > Yes, this is an issue that we were aware of for a long time and it
> > something that has made overlayfs somewhat more difficult to use than it
> > should be.
> > >
> > > Allegedly, this effort went underway to improve the experience of overlayfs
> > > users, who are mostly applications running inside containers. For backward
> > > compatibility reasons, container runtimes will need to opt-in for fixing some
> > > of the legacy behavior.
> > >
> > > In reality, I have seen very little cross list interaction between linux-unionfs
> > > and containers mailing lists. The only interaction I recall in the
> > > past two years
> > > ended up in a fix in overlayfs to require opt-in for fixing yet another backward
> > > compatible bad behavior, although docker did follow up shortly after to fix
> > > bad practice in container runtime:
> > > https://github.com/moby/moby/issues/34672
> > >
> > > So the questions I would like to relay to the micro-conf participants w.r.t the
> > > new opt-in overlayfs behavior:
> > > 1. Did you know?
> > I personally did not know about the new opt-in behavior. More reason to
> > give a talk! :)
> > > 2. Do you care?
> > Yes, we do care. However - speaking as LXC upstream now - we have
> > recently focused on getting shiftfs to work rather than overlayfs.
> IMO, as I expressed it in the past, the fact that shiftfs development is not
> collaborated with overlayfs developers is a pitty.
> Yes shiftfs has a different purpose than overlayfs, but they have common
> use cases and common problems as well.
My team hast just started to be more involved with shifts development a
few months back. Overlayfs is definitely an inspiration and we even once
thought about making shifts an extension of overlayfs.
Seth Forshee on my team is currently actively working on shifts and
getting a POC ready.
When he has a POC based on James' patchset there will be an RFC that
will go to fsdevel and all parties of interest.
There will also be an update on shifts development during the microconf.
So even more reason for developers from overlayfs to stop by.
> > We are more than happy to have a overlayfs talk at the microconf. If
> > someone were to talk about:
> > - What non-standard behavior has already been fixed?
> > - How has it been fixed?
> IMO, those questions are covered quite well by the wiki and overlayfs.txt
> documentation in kernel tree.
It's still worth bringing this in front of other developers in the form
of a talk.
> > - What non-standard behavior still needs to be fixed?
> There's the mmap MAP_SHARED case covered in the wiki
> and there may be other small stuff, but not sure if anyone cares
> about them, so the question should really be directed back to the audience...
The audience that cares enough to send patches for it will likely be at
the microconf so it's a good place to discuss it.
> > - Outstanding problems that either still need a solution or
> > are solved but one would like feedback on the implementation. This way
> > we can have a good discussion.
> I think one of the chsallange that distros and container runtime will need to
> deal with is managing format versions of overlay "images".
> The reason the new features require user or distro to opt-in is because
> the new features create overlayfs images that are not fully compatible with old
> kernels and existing container image tools (i.e. export/migrate image).
As I said we will be very thankful for any talk about such problems.
> The new overlayfs-progs project by Zhangyi is going to help in that respect:
> As well as Zhangyi's work on overlayfs feature set support:
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-09-09 14:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 16:10 Containers and checkpoint/restart micro-conference at LPC2018 Stéphane Graber
2018-09-08 4:59 ` Stéphane Graber
2018-09-08 7:41 ` Amir Goldstein
2018-09-09 1:31 ` Christian Brauner
2018-09-09 6:31 ` Overlayfs @ " Amir Goldstein
2018-09-09 9:18 ` Christian Brauner [this message]
2018-09-11 13:52 ` Vivek Goyal
2018-09-11 15:13 ` James Bottomley
2018-09-11 15:36 ` Vivek Goyal
2018-09-09 19:08 ` [lxc-users] " Lucas Oketch
2018-09-09 15:30 ` James Bottomley
2018-09-09 17:38 ` Steve French
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).