On 10/6/19 1:45 AM, Brad Hubbard wrote:
Working out what the selinux denial error is should
help to shed
light. The fact that relabeling the filesystem resolves the issue
could indicate that something in the past labelled it incorrectly to
begin with. I don't doubt running install-deps.sh could trigger this
issue but I strongly suspect the root cause lies with some bad system
package or update that results in an incorrectly labelled filesystem.
Just my 2c. In order to 'know' we would have to understand the problem
a lot better.
wonder if this reproduces in a VM?