Am Mittwoch, den 06.08.2014, 17:47 + schrieb Serge Hallyn:
Quoting Tom Weber (l_lxc-us...@mail2news.4t2.com):
Am Mittwoch, den 06.08.2014, 14:51 + schrieb Serge Hallyn:
Quoting Tom Weber (l_lxc-us...@mail2news.4t2.com):
Am Dienstag, den 05.08.2014, 23:34 + schrieb Serge
Hi folks,
is there some smart way to stop the rest of the containers
not stopped by lxc-autostart -s -a?
I would like to avoid the device busy at shutdown time, and
manually looping through all running containers reported by
lxc-ls appears a little bit clumsy.
Should I make lxc.start.auto=1
On Thu, Aug 07, 2014 at 04:33:15PM +0200, Harald Dunkel wrote:
Hi folks,
is there some smart way to stop the rest of the containers
not stopped by lxc-autostart -s -a?
lxc-autostart -s -A will do that with current git master, with older
LXC you're indeed stuck with either looping through
On Tue, 05 Aug 2014 13:53:58 +0200
Tom Weber l_lxc-us...@mail2news.4t2.com wrote:
Hello,
my setup:
debian7
lxc-1.0.4 from debian testing
vanilla kernel.org kernel 3.14.14
i'm new to lxc and apparmor, so this took me a couple of hours to
figure:
lxc-start won't assign an
Am Donnerstag, den 07.08.2014, 17:23 -0400 schrieb Dwight Engen:
On Tue, 05 Aug 2014 13:53:58 +0200
Tom Weber l_lxc-us...@mail2news.4t2.com wrote:
Oh, and a little log message wether lxc-start detected apparmor or not
and activates it would be _very_ helpfull :)
lsm_init() INFO()s which
