From: Christian Brauner <email@example.com> To: Amir Goldstein <firstname.lastname@example.org> Cc: Stephane Graber <email@example.com>, firstname.lastname@example.org, Miklos Szeredi <email@example.com>, Netdev <firstname.lastname@example.org>, overlayfs <email@example.com>, firstname.lastname@example.org, LSM List <email@example.com>, firstname.lastname@example.org, linux-fsdevel <email@example.com> Subject: Re: Containers and checkpoint/restart micro-conference at LPC2018 Date: Sun, 9 Sep 2018 03:31:08 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <CAOQ4uxiQEpofdS97kxnii8LtVW2QiKAGvjjaH0Px-Bj3eHVCFA@mail.gmail.com> [-- Attachment #1: Type: text/plain, Size: 3905 bytes --] On Sat, Sep 08, 2018 at 10:41:41AM +0300, Amir Goldstein wrote: > On Sat, Sep 8, 2018 at 8:00 AM Stéphane Graber <email@example.com> wrote: > > > > On Mon, Aug 13, 2018 at 12:10:15PM -0400, Stéphane Graber wrote: > > > Hello, > > > > > > This year's edition of the Linux Plumbers Conference will once again > > > have a containers micro-conference but this time around we'll have twice > > > the usual amount of time and will include the content that would > > > traditionally go into the checkpoint/restore micro-conference. > > > > > > LPC2018 will be held in Vancouver, Canada from the 13th to the 15th of > > > November, co-located with the Linux Kernel Summit. > > > > > > > > > We're looking for discussion topics around kernel work related to > > > containers and namespacing, resource control, access control, > > > checkpoint/restore of kernel structures, filesystem/mount handling for > > > containers and any related userspace work. > > > > > > > > > The format of the event will mostly be discussions where someone > > > introduces a given topic/problem and it then gets discussed for 20-30min > > > before moving on to something else. There will also be limited room for > > > short demos of recent work with shorter 15min slots. > > > > > > > > > Details can be found here: > > > > > > https://discuss.linuxcontainers.org/t/containers-micro-conference-at-linux-plumbers-2018/2417 > > > > > > > > > Looking forward to seeing you in Vancouver! > > > > Hello, > > > > We've added an extra week to the CFP, new deadline is Friday 14th of September. > > > > If you were thinking about sending something bug then forgot or just > > missed the deadline, now is your chance to send it! > > > > [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. 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? - What non-standard behavior still needs to be fixed? - 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. Thanks! Christian [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-09-09 1:31 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-08-13 16:10 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 [this message] 2018-09-09 6:31 ` Overlayfs @ " Amir Goldstein 2018-09-09 9:18 ` Christian Brauner 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
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Containers and checkpoint/restart micro-conference at LPC2018' \ /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
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).