is CONFIG_MEMCG mandatory for snappy?

[Jamie Strandboge]

On Wed, 2016-03-30 at 15:23 +0200, Paolo Pisati wrote:
> CONFIG_MEMCG is required per lxc documentation (see lxc-checkconfig),
> i don't know if it's strictly required for Ubuntu Core, but i'll let
> Jamie answer that.
> 
CONFIG_MEMCG isn't currently required for launching apps on Ubuntu Core itself
and looking at classic/*, it shouldn't break 'shell classic' either (the classic
shell isn't using lxc but is instead using systemd-run to run a shell in a
chroot).

The lxd and docker both have support for memory cgroups and these snaps are
likely to break.

> On Tue, Mar 29, 2016 at 6:32 PM, Yann Sionneau <yann.sionneau at parrot.com>
> wrote:
> > 
> > Hi,
> > 
> > I can see CONFIG_MEMCG is enabled in Snappy kernels:
> > http://kernel.ubuntu.com/git/ppisati/ubuntu-vivid.git/tree/arch/arm/configs/
> > snappy/lxc.config?h=snappy_v3.18&id=68e464017f7b0d00388689f70bb571ce96ef2659
> > #n15
> > 
> > From the arch/arm/configs/snappy/lxc.config
> > 
> > Is it only mandatory for the classic shell (using lxc)? Or is it also
> > mandatory for normal Snappy behaviour?
> > What would break without this?
> > 
> > Thanks!
> > 
> > Regards,
> > 
> > --
> > Yann
> > 
> > --
> > snappy-devel mailing list
> > snappy-devel at lists.ubuntu.com
> > Modify settings or unsubscribe at:
> > https://lists.ubuntu.com/mailman/listinfo/snappy-devel
> > 
> 
> 
-- 
Jamie Strandboge             | http://www.canonical.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <https://lists.ubuntu.com/archives/snappy-devel/attachments/20160330/5a01d7b2/attachment.pgp>