Hi all,
I just upgraded a server from bullseye to bookworm, and unfortunately this
issue is not fixed. I tried recreating the containers after the update, but it
did not help. I opted for the workaround to disable labeling for Podman in
/etc/containers/containers.conf. It's not ideal, but the i
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 are
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
a
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
> deb
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 needed
6 matches
Mail list logo
