Some where in this commit: 0bf4290c235b514c39ed9c8d3f3f2fbb95f60cfa ( in one of the file context specifications there ) is something that makes and breaks whatever creates the per user home directory contexts.
Without it, semodule (what use to be genhomedircon?) only creates contexts for the "__default__" login.
It took me almost a day to narrow it down to this. I would like to know which file context specification exactly is causing it and why
SELinux should and does BLOCK access to Docker socket - I get lots of bugs from people complaining about SELinux blocking access to the Docker socket. For example https://bugzilla.redhat.com/show_bug.cgi?id=1...
4 dagen geleden