If a container is running under a policy generated by udica and the container triggers some SELinux denials then these denials cannot be transformed into a local policy module via audit2allow but udica itself could be able to update the policy and users would use udica instead of audit2allow.
If a container is running under a policy generated by udica and the container triggers some SELinux denials then these denials cannot be transformed into a local policy module via audit2allow but udica itself could be able to update the policy and users would use udica instead of audit2allow.
e.g.
this would update my_container.cil with rules needed for container to bind to port 22 and user would just install the module again.
https://bugzilla.redhat.com/show_bug.cgi?id=1732704
Idea by @bachradsusi .