reassign 783106 libvirt thanks On 04/29/2015 05:53 PM, Nikolay conShaplov wrote: > I've commented out all lxc.network.* options, and container started > successfully on reboot.
so the problem is not in lxc but in (a race condition) on how your network is brought up. lxc already has a 'start this after network', so there is nothing we can do on this end, reassigning to libvirt. > I far as I can get libvrt is a > valid tool for this task, it is described in debian's wiki the wiki wrt/ lxc is not maintained, it has random information copied from somewhere. just because it's in the internet (the wiki), it's not automatically right. further more, yes, it doesn't matter which technology you use to setup up the bridge, but if you leave the default path (ifupdown), you get bugs. Regards, Daniel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
