> The alternative is to go on the node and run "setsebool container_manage_cgroup 1" and then you won't need to set privileged to true.
The bug is that I need privileged. I wouldn't consider this fixed if I still need privileged to run the pod.
It already worked with privileged before any of this work.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.