You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Windows build number: 20185
CentOS 7 , upgraded: [Linux version 4.19.121-microsoft-standard
WSL 2
Steps to reproduce
Expected behavior
systemctl functions as described in Linux systenctl documentation in Selinux hardened distros when SELINUX is disabled in its configuration file.
Actual behavior
Almost every systemctl operation ends with “Operation not permitted”.
This is known issue with SELINUX configuration described in Selinux configuration.
extra lines in the configuration file.
But, Either as a part of the upgrade or as a "minimal CentOS7 distro" gotten from MSStore I get /etc/sysconfig/selinux with 2 extra lines.
Please, check CentOS 7 distro!
The text was updated successfully, but these errors were encountered:
Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.
Hint: Disable SELINUX in the kernel paramemters
Question: whether Active SELINUX is necessary for WSL2 distro by default?
Pros: it was added because NSA wanted it and it's a part of the security certificate.
Cons: It is unusable in 90% of scenarios, like the same laptop is used at home and office.
Environment
Steps to reproduce
Expected behavior
systemctl functions as described in Linux systenctl documentation in Selinux hardened distros when SELINUX is disabled in its configuration file.
Actual behavior
Almost every systemctl operation ends with “Operation not permitted”.
This is known issue with SELINUX configuration described in Selinux configuration.
extra lines in the configuration file.
But, Either as a part of the upgrade or as a "minimal CentOS7 distro" gotten from MSStore I get /etc/sysconfig/selinux with 2 extra lines.
Please, check CentOS 7 distro!
The text was updated successfully, but these errors were encountered: