AlmaLinux on WSL initscripts
![](https://seccdn.libravatar.org/avatar/bb0fcdcf82f7cba144cc9f27487e9a70.jpg?s=120&d=retro&r=g)
Hello, I’m having an issue with Windows 10, WSL, and AlmaLinux 8. WSL is at version 1.0.3.0 so what I am trying to do should work. But since it’s easy to blame Microsoft, I am going to do that for the time being. 😊 I am trying to use systemd within WSL running AlmaLinux. AlmaLinux is fully updated on 8.7. I edited /etc/wsl.conf to include [boot] and setting systemd as true. I’ve restarted WSL (and the Windows computer), and still for the life of me, I cannot get AlmaLinux to load systemd. The fallback should be using initscripts. Obviously, RHEL (so AlmaLinux), have moved to systemd but there is an initscripts package. I installed that and even restarted WSL for good measure, but unfortunately it redirects service to systemctl and then it complains that the system was booted as init and not systemd and it can’t operate. So my question is, has anyone either got systemd working on AlmaLinux under WSL or has anyone got initscripts working? I’ve been Googling this like mad but all I’ve been able to find are articles regarding Ubuntu. Thanks in advance if anyone can provide some insight! Kind regards, Travis Newton Founder/Owner Hosting Intellect, LLC (Formerly Xinsto, LLC) [Hosting Intellect, LLC Logo] https://www.hostingintellect.comhttps://www.hostingintellect.com/ -- This e-mail and any attached files are confidential and may be legally privileged. If you are not the addressee, any disclosure, reproduction, copying, distribution, or other dissemination or use of this communication is strictly prohibited. If you have received this transmission in error please notify the sender immediately and then delete this mail. E-mail transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission or changes to transmitted date not specifically approved by the sender. If this e-mail or attached files contain information which do not relate to our professional activity we do not accept liability for such information.
![](https://seccdn.libravatar.org/avatar/520b5c83478d50ce06be511d74554339.jpg?s=120&d=retro&r=g)
On 2/23/2023 1:41 PM, Travis Newton wrote:
Hello,
I’m having an issue with Windows 10, WSL, and AlmaLinux 8. WSL is at version 1.0.3.0 so what I am trying to do should work. But since it’s easy to blame Microsoft, I am going to do that for the time being. 😊
I am trying to use systemd within WSL running AlmaLinux. AlmaLinux is fully updated on 8.7. I edited /etc/wsl.conf to include [boot] and setting systemd as true. I’ve restarted WSL (and the Windows computer), and still for the life of me, I cannot get AlmaLinux to load systemd.
The fallback should be using initscripts. Obviously, RHEL (so AlmaLinux), have moved to systemd but there is an initscripts package. I installed that and even restarted WSL for good measure, but unfortunately it redirects service to systemctl and then it complains that the system was booted as init and not systemd and it can’t operate.
So my question is, has anyone either got systemd working on AlmaLinux under WSL or has anyone got initscripts working?
I’ve been Googling this like mad but all I’ve been able to find are articles regarding Ubuntu.
Thanks in advance if anyone can provide some insight!
Your /etc/wsl.conf file should have the following two lines in it, exactly as shown below: [boot] systemd=true I'm running AlmaLinux 9 in WSL and systemd is up and running. Screenshot here: https://i.imgur.com/CatAvvv.png Scott
![](https://seccdn.libravatar.org/avatar/bb0fcdcf82f7cba144cc9f27487e9a70.jpg?s=120&d=retro&r=g)
Scott,
I do have the same configuration within AlmaLinux 8. However, I just downloaded AlmaLinux 9 for WSL, added
[boot]
System=true
to /etc/wsl.conf and systemd works as expected.
Thanks for the confirmation that it does work. So it's either a bug in AlmaLinux 8 or there's something wrong with the image I have.
Kind regards,
Travis Newton
Founder/Owner
Hosting Intellect, LLC (Formerly Xinsto, LLC)
https://www.hostingintellect.com
-----Original Message-----
From: Scott Beamer
Hello,
I’m having an issue with Windows 10, WSL, and AlmaLinux 8. WSL is at version 1.0.3.0 so what I am trying to do should work. But since it’s easy to blame Microsoft, I am going to do that for the time being. 😊
I am trying to use systemd within WSL running AlmaLinux. AlmaLinux is fully updated on 8.7. I edited /etc/wsl.conf to include [boot] and setting systemd as true. I’ve restarted WSL (and the Windows computer), and still for the life of me, I cannot get AlmaLinux to load systemd.
The fallback should be using initscripts. Obviously, RHEL (so AlmaLinux), have moved to systemd but there is an initscripts package. I installed that and even restarted WSL for good measure, but unfortunately it redirects service to systemctl and then it complains that the system was booted as init and not systemd and it can’t operate.
So my question is, has anyone either got systemd working on AlmaLinux under WSL or has anyone got initscripts working?
I’ve been Googling this like mad but all I’ve been able to find are articles regarding Ubuntu.
Thanks in advance if anyone can provide some insight!
Your /etc/wsl.conf file should have the following two lines in it, exactly as shown below: [boot] systemd=true I'm running AlmaLinux 9 in WSL and systemd is up and running. Screenshot here: https://i.imgur.com/CatAvvv.png Scott _______________________________________________ AlmaLinux Users mailing list -- users@lists.almalinux.org To unsubscribe send an email to users-leave@lists.almalinux.org -- This e-mail and any attached files are confidential and may be legally privileged. If you are not the addressee, any disclosure, reproduction, copying, distribution, or other dissemination or use of this communication is strictly prohibited. If you have received this transmission in error please notify the sender immediately and then delete this mail. E-mail transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission or changes to transmitted date not specifically approved by the sender. If this e-mail or attached files contain information which do not relate to our professional activity we do not accept liability for such information.
![](https://seccdn.libravatar.org/avatar/520b5c83478d50ce06be511d74554339.jpg?s=120&d=retro&r=g)
On 2/24/2023 5:42 AM, Travis Newton wrote:
Scott,
I do have the same configuration within AlmaLinux 8. However, I just downloaded AlmaLinux 9 for WSL, added
[boot] System=true
to /etc/wsl.conf and systemd works as expected.
Thanks for the confirmation that it does work. So it's either a bug in AlmaLinux 8 or there's something wrong with the image I have.
You're welcome. I'm glad you got it working. Scott
participants (2)
-
Scott Beamer
-
Travis Newton