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

"System has not been booted with systemd as init system (PID 1). Can't operate" when i run timedatectl command in WSL1 #6739

Closed
ZihaoXingUP opened this issue Mar 31, 2021 · 3 comments

Comments

@ZihaoXingUP
Copy link

image

@shawnz
Copy link

shawnz commented Mar 31, 2021

That is expected. Timedatectl only works with systemd which is not used in WSL1.

@therealkenc
Copy link
Collaborator

therealkenc commented Mar 31, 2021

This is effectively dupe #1579 ➡️ #994. The systemd-timesyncd service is not running (on WSL1 or WSL2). This ask has different specifics than systemctl(1), but any out-of-box solution for WSL2 systemd would in all likelihood address both. In the event #1579 flips status but timedatectl(1) is still not supported out of the box we can revisit/reopen.

@ghost
Copy link

ghost commented Mar 31, 2021

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.

Thanks for your report!

@ghost ghost closed this as completed Mar 31, 2021
@ghost ghost added the duplicate label Mar 31, 2021
This issue was closed.
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

3 participants