Bug#783106: lxc container does not start automatically
On Thu, Apr 30, 2015 at 07:08:13PM +0200, Daniel Baumann wrote: On 04/30/15 08:50, Guido Günther wrote: * lxc is lacking error reporting if you start it via initscript and have no error-logging, then indeed you don't see any error. * doesn't wait for libvirt to come up - it's debatable wether this would be a good thing no; both the initscript and the systemd unit have network as a depends - there's nothing more we can do on the lxc (or any other service that requires network to be up) side. I would totally agree that libvirt has a bug if the lxc container would be libvirt managed (via lxc://) but this isn't the case. right; but the user is abusing libvirt here to setup his bridge, rather than to configure it normally. it's up to you though if you want to 'allow' users to use libvirt like that or not. We we won't lose anything if we add a Should-Start: libvirtd, do we? Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783106: lxc container does not start automatically
On 05/01/15 19:50, Guido Günther wrote: We we won't lose anything if we add a Should-Start: libvirtd, do we? the reason for network is to not need to list all packages that provide network. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783106: lxc container does not start automatically
В письме от 30 апреля 2015 08:50:04 пользователь Guido Günther написал: On Wed, Apr 29, 2015 at 06:53:59PM +0300, Nikolay Shaplov wrote: В письме от 29 апреля 2015 08:01:24 пользователь Daniel Baumann написал: Hi, could you reproduce it without libvirt? I've commented out all lxc.network.* options, and container started successfully on reboot. But I still think this is a bug. Because 1. It does not give any reasonable description in error log 2. It should work. I far as I can get libvrt is a valid tool for this task, it is described in debian's wiki, and I see no reason why it should not be used in start on boot case. Boot script should be fixed. I don't see what libvirt could do here. From the report it seems * lxc is lacking error reporting * doesn't wait for libvirt to come up - it's debatable wether this would be a good thing Yeah, that's exactly what I am trying to say ;-) I would totally agree that libvirt has a bug if the lxc container would be libvirt managed (via lxc://) but this isn't the case. Cheers, -- Guido signature.asc Description: This is a digitally signed message part.
Bug#783106: lxc container does not start automatically
On Wed, Apr 29, 2015 at 06:53:59PM +0300, Nikolay Shaplov wrote: В письме от 29 апреля 2015 08:01:24 пользователь Daniel Baumann написал: Hi, could you reproduce it without libvirt? I've commented out all lxc.network.* options, and container started successfully on reboot. But I still think this is a bug. Because 1. It does not give any reasonable description in error log 2. It should work. I far as I can get libvrt is a valid tool for this task, it is described in debian's wiki, and I see no reason why it should not be used in start on boot case. Boot script should be fixed. I don't see what libvirt could do here. From the report it seems * lxc is lacking error reporting * doesn't wait for libvirt to come up - it's debatable wether this would be a good thing I would totally agree that libvirt has a bug if the lxc container would be libvirt managed (via lxc://) but this isn't the case. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783106: lxc container does not start automatically
On 04/30/15 08:50, Guido Günther wrote: * lxc is lacking error reporting if you start it via initscript and have no error-logging, then indeed you don't see any error. * doesn't wait for libvirt to come up - it's debatable wether this would be a good thing no; both the initscript and the systemd unit have network as a depends - there's nothing more we can do on the lxc (or any other service that requires network to be up) side. I would totally agree that libvirt has a bug if the lxc container would be libvirt managed (via lxc://) but this isn't the case. right; but the user is abusing libvirt here to setup his bridge, rather than to configure it normally. it's up to you though if you want to 'allow' users to use libvirt like that or not. Regards, Daniel -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783106: lxc container does not start automatically
Hi, could you reproduce it without libvirt? Regards, Daniel -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783106: lxc container does not start automatically
В письме от 29 апреля 2015 08:01:24 пользователь Daniel Baumann написал: Hi, could you reproduce it without libvirt? I've commented out all lxc.network.* options, and container started successfully on reboot. But I still think this is a bug. Because 1. It does not give any reasonable description in error log 2. It should work. I far as I can get libvrt is a valid tool for this task, it is described in debian's wiki, and I see no reason why it should not be used in start on boot case. Boot script should be fixed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783106: lxc container does not start automatically
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
Bug#783106: lxc container does not start automatically
В письме от 22 апреля 2015 11:42:58 Вы написали: tag 783106 unreproducible tag 783106 moreinfo severity 783106 minor thanks On 04/22/15 11:25, Nikolay Shaplov wrote: Apr 22 11:59:12 nataraj-pgpro lxc-autostart-helper[974]: Starting LXC autoboot containers: :Error starting container: pgbuild i suggest you look into this, probably your container needs something in its config that you haven't got ready by the time lxc-autostart runs. Thank you, captain obvious! Can you tell how to find out what does it needs? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783106: lxc container does not start automatically
Package: lxc Version: 1:1.0.6-6 Severity: normal https://wiki.debian.org/LXC#Debian_8_.22Jessie.22.2Ftesting I've added lxc.start.auto = 1 into /var/lib/lxc/pgbuild/config as I did on ubuntu but my container does not start on reboot # lxc-ls -f NAME STATEIPV4 IPV6 AUTOSTART --- pgbuild STOPPED - - YES syslog says: # grep lxc /var/log/syslog Apr 22 11:59:06 nataraj-pgpro lxc-devsetup[665]: Creating /dev/.lxc Apr 22 11:59:06 nataraj-pgpro lxc-devsetup[665]: /dev is devtmpfs Apr 22 11:59:06 nataraj-pgpro lxc-devsetup[665]: Creating /dev/.lxc/user Apr 22 11:59:12 nataraj-pgpro lxc-autostart-helper[974]: Starting LXC autoboot containers: :Error starting container: pgbuild meanwhile I can easily start it manually # lxc-start -n pgbuild -d # lxc-ls -f NAME STATEIPV4 IPV6 AUTOSTART -- pgbuild RUNNING 192.168.122.101 - YES I think there is some bug... Can you help me how to debug it, as I did not find any logs from lxc-autostart-helper or something like that. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.14-2-686-pae (SMP w/8 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lxc depends on: ii init-system-helpers 1.22 ii libapparmor1 2.9.0-3 ii libc62.19-18 ii libcap2 1:2.24-8 ii libseccomp2 2.1.1-1 ii libselinux1 2.3-2 ii multiarch-support2.19-18 ii python3 3.4.2-2 Versions of packages lxc recommends: ii debootstrap 1.0.67 ii openssl 1.0.1k-3 ii rsync3.1.1-3 Versions of packages lxc suggests: pn lua5.2 none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783106: lxc container does not start automatically
tag 783106 unreproducible tag 783106 moreinfo severity 783106 minor thanks On 04/22/15 11:25, Nikolay Shaplov wrote: Apr 22 11:59:12 nataraj-pgpro lxc-autostart-helper[974]: Starting LXC autoboot containers: :Error starting container: pgbuild i suggest you look into this, probably your container needs something in its config that you haven't got ready by the time lxc-autostart runs. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783106: lxc container does not start automatically
On 04/22/15 11:57, Nikolay Shaplov wrote: i suggest you look into this, probably your container needs something in its config that you haven't got ready by the time lxc-autostart runs. Thank you, captain obvious! you're welcome. Can you tell how to find out what does it needs? no, because you didn't give any information about your container at all. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783106: lxc container does not start automatically
В письме от 22 апреля 2015 12:48:00 пользователь Daniel Baumann написал: On 04/22/15 11:57, Nikolay Shaplov wrote: i suggest you look into this, probably your container needs something in its config that you haven't got ready by the time lxc-autostart runs. Thank you, captain obvious! you're welcome. Can you tell how to find out what does it needs? no, because you didn't give any information about your container at all. As I already said: container configured as said in https://wiki.debian.org/LXC#Debian_8_.22Jessie.22.2Ftesting Network configured as said in https://wiki.debian.org/LXC/LibVirtDefaultNetwork and added lxc.start.auto = 1 to the config file if you need more information, just tell me where to get it, and I will give it to you... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783106: lxc container does not start automatically
On 04/22/15 13:14, Nikolay Shaplov wrote: Network configured as said in https://wiki.debian.org/LXC/LibVirtDefaultNetwork try not using libvirt but configuring a bridge in /etc/network/interfaces instead. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
