Docker 0-Day Stopped Cold by SELinux
SELinux used to be one of those things you&#x27;d disable immediately upon installing a new RHEL&#x2F;CentOS box for all the troubles it would cause. But default policies have evolved a lot, making this the wrong thing to do, for a few years now. But people still do it out of habit.<p>If you ignore SELinux, it won&#x27;t cause issues besides the ocasional need to run &quot;restorecon&quot; (which one gets into the habit of doing whenever an &quot;access denied&quot; error happens when permissions seem otherwise correct).<p>But one problem still remains. SELinux is (very) complex and people (myself included) have a very hard time groking its base concepts. This limits adoption greatly, and I&#x27;m still to find a decent document that starts from the simple stuff and lets one build a mental concept of how it works before jumping into the more complicated (real-world) use cases.