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. #3707
Comments
I am also facing the same problem... |
I got this error after doing these:
|
I had this problem running WSL 2 the solution was the command
Open other terminal and try it
if after that you still have a problem with permission, run the command:
|
My bad. I was not following the official guide to integrate WSL with Docker. I run into that problem because I install docker from inside WSL with So, follow the guide to integrate WSL with Docker Desktop. |
|
@ifaniqbal what guide did you followed? |
Hi, you can follow these guidelines:
https://docs.microsoft.com/en-us/windows/wsl/install-win10
https://docs.docker.com/docker-for-windows/wsl/
|
When installed tomcat and run command "systemctl daemon-reload", I got "System has not been booted with systemd as init system (PID 1). Can't operate", is this kind of beyond WSL supported function, or have some sort of work around etc?
The text was updated successfully, but these errors were encountered: