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.
