On 04/01/2014 01:19 PM, Chris St. Pierre wrote:
On Tue, Apr 1, 2014 at 8:07 AM, Matthew Miller <mattdm@mattdm.org mailto:mattdm@mattdm.org> wrote:
On Tue, Apr 01, 2014 at 01:01:54AM +0100, Karanbir Singh wrote: > Known Issues: > * There seem to be some selinux issues ( afaict, leaving libselinux > intact would fix that ) *Inside* the container, or from outside? selinux isn't namespaced and so can't work inside.
It should only be inside the container -- I tore out the SELinux stuff for precisely this reason, so I wouldn't expect it to work inside.
with selinux enforcing outside the container - nothing works inside the container, failing with libselinux errors.