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
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:
В письме от 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
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
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
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
В письме от 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
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
В письме от 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:
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
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
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
В письме от 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!
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:
14 matches
Mail list logo
