[Bug 1227313] Re: Error parsing lxc-start apparmor profile

This package (0.9.0-0ubuntu3.6) fixes the bug for me. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1227313 Title:

[Bug 1227313] Re: Error parsing lxc-start apparmor profile

1215391 is fixed now. This can now be pushed to raring-proposed, right? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1227313 Title: Error parsing lxc-start apparmor profile To

[Bug 1215391] Re: lxc-start can't parse IPv6 addresses

This package (0.9.0-0ubuntu3.5) fxies the bug for me. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1215391 Title:

[Bug 1227313] [NEW] Error parsing lxc-start apparmor profile

Public bug reported: The lxc-start package reads its apparmor profile from /proc/$PID/attr/current but does not remove the trailing newline character. When trying to run an unconfined container, this causes comparisons with the unconfined string in the source code to fail, and the apparmor

[Bug 1215386] Re: lxc-start tries to change apparmor profile to unconfined

Just to confirm, the bug wrt the apparmor profile is indeed fixed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1215386 Title: lxc-start tries to change apparmor profile to

[Bug 1215386] Re: lxc-start tries to change apparmor profile to unconfined

You are correct, the error I'm seeing comes from the fact that I have this line on the container's fstab: proc /var/lib/lxc/test/rootfs/proc proc ro,nodev,noexec,nosuid 0 0 That is, I was trying to mount /proc as read-only in the container. This works for me in 12.04 but not in 13.04. -- You

[Bug 1215386] Re: lxc-start tries to change apparmor profile to unconfined

I tried it with /etc/apparmor.d/usr.bin.lxc-start both enabled and disabled, and also with and without lxc.aa_profile = unconfined in the configuration file and all tests worked fine in the four possible combinations of those settings. -- You received this bug notification because you are a

[Bug 1215386] Re: lxc-start tries to change apparmor profile to unconfined

Hi The issue is still not fixed with the patch. While there's no more garbage in the buffer that stores the apparmor profile read from /proc, that data is still terminated by a \n, (ie., the profile is returned as, eg. unconfined\n instead of unconfined). This causes comparisons with the

[Bug 1215386] [NEW] lxc-start tries to change apparmor profile to unconfined

Public bug reported: When starting a container that has 'lxc.aa_profile = unconfined' on its configuration file, lxc-start fails with lxc-start: Read-only file system - failed to change apparmor profile to unconfined This happens because the buffer used by lxc-start to read the process'

[Bug 1215391] [NEW] lxc-start can't parse IPv6 addresses

Public bug reported: A container with an IPv6 address in its configuration (for example, 'lxc.network.ipv6 = 2001:db8:fedc:abcd::2/80') fails to start with the error below. lxc-start 1377083732.942 ERRORlxc_confile - No such file or directory - invalid ipv6 address:

[Bug 683601] [NEW] Class-level dependencies not honored

Public bug reported: Binary package hint: puppet Hello There's a bug in Puppet 0.25.4 that breaks class-level dependency handling when using the require function multiple times: http://projects.puppetlabs.com/issues/3186 The fix is a one-liner: