Hello
I've found the following issue running lxc-start on Ubuntu 13.04:
lxc-start: Read-only file system - failed to change apparmor profile
to unconfined
This happens despite "lxc.aa_profile = unconfined" being set in the
container configuration. What happened was that aa_am_unconfined() was
returning false, and investigating why I found that the string returned
by aa_get_profile() was "unconfined\n/tty1" instead of simply "unconfined".
So adding this bit of code at the end of aa_get_profile() fixed the
issue for me:
space = index(buf, '\n');
if (space)
*space = '\0';
Has anyone seen this before? I'm not sure if this is a kernel bug (since
the profile is being read from /proc) or an lxc bug... I'm using kernel
3.8.0-27-generic and lxc 0.9.0-0ubuntu3.4.
There's a second issue: if I add an IPv6 address to the configuration, as in
lxc.network.ipv6 = 2001:db8:fedc:abcd::2/80
it used to work on 12.04 but on 13.04 I get the following error:
lxc-start 1377083732.942 ERROR lxc_confile - No such file or
directory - invalid ipv6 address: 2001:db8:fedc:abcd::2/80
Is this known?
Thanks
Andre
------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
_______________________________________________
Lxc-devel mailing list
Lxc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-devel
