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: 24 >> Policy from config file: targeted >> >> which disables selinux obviously. > ... *not* > > Interesting, in the container: > > [root@pgsql ~]# setenforce 0 > setenforce: setenforce() failed > > ??? not possible???
Even after more thinking about - do you mean disable SELinux on host? This would make sense for me, since the host kernel has SELinux - using the same kernel in a disabled container would disable it on host self also, probably not intentionally - isn't it? ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
