Hi Laurent & Sam,
On Thu, May 13, 2021 at 10:14:38AM +0200, Laurent Bigonville wrote:
> I see that you reassigned this bug to the refpolicy package and FTR I don't
> completely agree with that.
>
> Most of the other applications that manipulates SELinux objects are behaving
> nicely when they
On Wed, Jun 21, 2023 at 06:04:14PM +0100, Sam Morris wrote:
> On Wed, Jun 21, 2023 at 05:28:48PM +0100, Sam Morris wrote:
> > refpolicy has a 'container' module that appears to work, it's just not
> > built by default.
>
> BTW, the existance of /etc/selinux/default/contexts/lxc_contexts is what
>
On Wed, Jun 21, 2023 at 05:28:48PM +0100, Sam Morris wrote:
> refpolicy has a 'container' module that appears to work, it's just not
> built by default.
BTW, the existance of /etc/selinux/default/contexts/lxc_contexts is what
causes Podman to try to label containers. Which prevents it from being
On Thu, May 13, 2021 at 10:14:38AM +0200, Laurent Bigonville wrote:
> From a SELinux policy perspective, the main problem is that the "container"
> policy is 100% Red Hat specific and has not been upstreamed and the
> difficulty is that the RH SELinux policy is heavily patched compared to the
>
1234
Date: Thu, 13 May 2021 10:14:38 +0200
>From: Laurent Bigonville
>-
>Body: Package: podman
>Version: 3.0.1+dfsg1-1
>Severity: serious
>
>Hello,
>
>I'm trying to run a container using podman (podman run -ti debian
>/bin/bash) as root and as non-root and I get the same error in both
Hello Reinhard,
I see that you reassigned this bug to the refpolicy package and FTR I
don't completely agree with that.
Most of the other applications that manipulates SELinux objects are
behaving nicely when they are running in permissive and the policy is
not including the type they
Package: podman
Version: 3.0.1+dfsg1-1
Severity: serious
Hello,
I'm trying to run a container using podman (podman run -ti debian
/bin/bash) as root and as non-root and I get the same error in both
cases:
Error: failed to mount shm tmpfs
8 matches
Mail list logo
