I understand many people require the enhanced security of SELinux and all that brings.
One of the main purposes and strong benefits of containerized architectures (like Docker) is that containerized applications can run on any underlying architecture as long as the container management system (in this Discourse case, Docker) is working.
My thoughts, for what it is worth, is that an application development team should not go down the rabbit-hole of supporting every requested OS distribution (non-standard) Docker install. That defeats one of the main purposes of running a containerized architecture.
More maintainable, in my view, is for sys admins to insure their Docker installation are working in a standard way, and if their Docker setup is not matching the “Discourse standard”, then they should add symbolic links to binaries, files and directories to match mainstream standard Docker configurations.
OS distributions can and do change at any time, and this includes the configuration for installed applications. If an application team (like Discourse, for example) begins expanding their setup files to adapt to various Docker configuration, then they will have to track each OS distribution for changes with each new OS distribution release.
For us, if we were going to run Discourse on SELinux (we run on Ubuntu, BTW), we would more-than-likely start by writing a script to create the required symbolic links for SELinux to match the required Docker files as installed and configured in the standard distribution supported by Discourse.
I did a quick check of a few VPS providers for you and thought I might do this (create the script for you) if I could get a SELinux distribution setup on a cheap VPS. Unfortunately, the VPS providers I use (Linode and Digital Ocean) do not offer SELinux so I abandoned the idea.
Do you know of any “cheap, reliable VPS” provider where I can set up SELinux quickly?