Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sysctl failed to get properties no such interface #2787

Closed
weirdbeardgame opened this issue Dec 26, 2017 · 1 comment
Closed

sysctl failed to get properties no such interface #2787

weirdbeardgame opened this issue Dec 26, 2017 · 1 comment

Comments

@weirdbeardgame
Copy link

Build: 17063

any sysctl command is met with sysctl failed to get properties no such interface

Sysctl should allow me to see the status of services without error as well as modify and enable

sort of work around
sudo rsync -a /lib/systemd/system/ /etc/systemd/system/

all .service files in wsl are by default located in the /lib folder mentioned above whilst they should be in the /etc equivalent. doing the above command fixes the above initial error but we are instead met with

when running systemctl status
Failed to read server status: Operation not permitted
regardless of whether I run as sudo or not.

subsequently attempting to work with properties gives a subsequent error
Failed to get properties: Access denied
most work around's suggest setenforce 0 to get past said permission error but Selinux is inoperable at this time in wsl.

If the wsl team could move the file locations and fix permissions we might see systemd start.

@therealkenc
Copy link
Collaborator

therealkenc commented Dec 26, 2017

There is an open issue on systemd #994. I'll get you over there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants