View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000190 | AlmaLinux-8 | selinux-policy | public | 2022-02-22 15:04 | 2022-04-29 10:07 |
| Reporter | Blackclaws | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | new | Resolution | open | ||
| Summary | 0000190: k3s selinux not working on Almalinux | ||||
| Description | The k3s selinux package does not work correctly on Almalinux in contrast to CentOS 8.5. By my understanding this should work out of the box as Almalinux is more or less a drop in replacement. Is this something the package has to address or is this something that Almalinux has to address? There is a related bug on github: https://github.com/k3s-io/k3s-selinux/issues/27 | ||||
| Steps To Reproduce | See github bug. | ||||
| Additional Information | Works on CentOS 8.5 not tested on RHEL so far | ||||
| Tags | No tags attached. | ||||
| abrt_hash | |||||
| URL | |||||
|
|
The reason why I classified this as major is because the update to Almalinux 8.5 broke my k3s cluster due to this issue. I had to deactivate SELinux in the meantime to resolve. As stated above it might not actually be Almalinux fault but I don't understand enough about how the policy systems might differ to correctly pin down the source of the problem. |
|
|
@Blackclaws, GitHub issue indicates that this has been resolved on package update. Please verify. |
|
|
Unfortunately that doesn't seem to be the case. I still need to run with setenforce 0 in order to be able to run most containers. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-02-22 15:04 | Blackclaws | New Issue | |
| 2022-02-22 15:06 | Blackclaws | Note Added: 0000496 | |
| 2022-03-26 10:48 | srbala | Note Added: 0000523 | |
| 2022-04-29 10:07 | Blackclaws | Note Added: 0000550 |
