On 10/23/2012 12:29 AM, Ulli Horlacher wrote:
On Mon 2012-10-22 (14:53), Stéphane Graber wrote:
All in all, that's somewhere around 300-400 containers I'm managing
How do you handle a host (hardware) failure?
Everything that runs in the container is in a configuration management
system, so
On 10/23/2012 12:05 AM, Michael H. Warfield wrote:
On Mon, 2012-10-22 at 16:21 -0500, Serge Hallyn wrote:
Quoting Michael H. Warfield (m...@wittsend.com):
On Mon, 2012-10-22 at 15:14 -0500, Serge Hallyn wrote:
Trimming some overhead we've seen enough of...
How about just a devtmpfs? We
to be more precise, I've got after root/passwd phrase the option:
Would you like to enter a security context? [N]
Looks like selinux problem? Can you try disabling selinux in the host
(and possibly in the guest as well) with setenforce 0.
FWIW in my experience doing setenforce 0
in the the lxc container I can do now
[root@pgsql ~]# sestatus
SELinux status: enabled
SELinuxfs mount:/selinux
Current mode: enforcing
Mode from config file: disabled
Policy version: 24
Policy from config file:
Am 23.10.2012 20:10, schrieb olx69:
in the the lxc container I can do now
[root@pgsql ~]# sestatus
SELinux status: enabled
SELinuxfs mount:/selinux
Current mode: enforcing
Mode from config file: disabled
Policy version:
On Tue, 23 Oct 2012 20:03:33 +0200
olx69 ope-li...@gmx.de wrote:
to be more precise, I've got after root/passwd phrase the
option:
Would you like to enter a security context? [N]
Looks like selinux problem? Can you try disabling selinux in the
host (and possibly in the
