Hi,
if lxc.aa_allow_incomplete=1 doesn't fix it for you, then you probably
have another bug. Would you mind filing a new bug about your issue? Please
start the container with 'lxc-start -n container_name -l trace -o debug.out'
and append the debug.out file to the new bug.
--
You received this
Can someone clarify exactly what the work around for this bug is? I've
been bitten by it but adding "lxc.aa_allow_incomplete = 1" to either my
container config or the /etc/lxc/default.conf don't seem to resolve it
for me.
--
You received this bug notification because you are a member of Ubuntu
Bu
We are working around important functionality being missing from
the kernel. I'd prefer that the apparmor mount functionality go
upstream sooner, rather then spend time (and risk regressions)
working around it better.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
It'd be nice to validate the prerequisites (e.g. in `debconf` or at
start) and fail with a better feedback (either at start, through package
dependencies or a debconf warning (that the program can't be used or
needs to be reconfigured)) or change default settings at installation.
--
You received
Your kernel does not have the apparmor patchset to support mount
restrictions. So long as tha tis the case, your workaround is the
correct one. Note that (privileged) containers are less secure this
way, although unprivileged containers should be ok.
** Changed in: lxc (Ubuntu)
Status: In
I just realize that I added `lxc.aa_allow_incomplete = 1` to the lxc
`config` file before the initial issue. Now after adding the very same
line the issue disappeared, i.e. I can start the lxc `p2`. What now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
1. network configuration:
$ env LANG=C ifconfig -a`
eth1 Link encap:Ethernet HWaddr 00:00:0b:00:0d:8d
inet addr:192.168.178.22 Bcast:192.168.178.255
Mask:255.255.255.0
inet6 addr: fe80::200:bff:fe00:d8d/64 Scope:Link
UP BROADCAST RUNNING
(Note that I cannot reproduce this here; sudo lxc-create -t ubuntu -n
p1 -- -r precise -a i386 results in a working container for me. So we
need to figure out what is differnet in your environment.)
** Changed in: lxc (Ubuntu)
Status: New => Incomplete
--
You received this bug notificat
Thanks for taking the time to report this bug. Certainly as root you
should be able to attach devices to lxcbr0.
Could you please
1. show the result of 'ifconfig -a' and 'brctl show'
2. do 'sudo lxc-start -n Ubuntu-12.04.5-i386 -f -l trace -o lxc.debug' and
attach lxc.debug here
3. try:
sudo
