You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am technically using Tumbleweed, not MicroOS, but I am able to match the package versions of the initial raiser.
To be honest, I'm not really sure if this is a k3s-selinux bug or a selinux-policy-targeted bug. I tried to reproduce on RKE2, but I hit rancher/rke2-selinux#56 for now.
The problem manifests when upgrading selinux-policy-targeted from 20231012-1.1 to 120231030-1.1.
Before the upgrade, privileged containers run correctly in the spc_t domain.
Found this while investigating longhorn/longhorn#5348 (comment).
I am technically using Tumbleweed, not MicroOS, but I am able to match the package versions of the initial raiser.
To be honest, I'm not really sure if this is a
k3s-selinux
bug or aselinux-policy-targeted
bug. I tried to reproduce on RKE2, but I hit rancher/rke2-selinux#56 for now.The problem manifests when upgrading
selinux-policy-targeted
from20231012-1.1
to120231030-1.1
.Before the upgrade, privileged containers run correctly in the
spc_t
domain.After the upgrade, they stay in the
container_runtime_t
domain. This is the root cause of longhorn/longhorn#5348 (comment).Other context:
k3s version:
v1.27.7+k3s2
OS distribution:
The text was updated successfully, but these errors were encountered: