Windows 10: Is Service on wsl running on background ?

Hello I am new on wsl / wsl2 here, currently I am using win 11, if I'm using wsl2 on my windows, let say using ubuntu distro, and I'm running service on my wsl ubuntu like postgre, mongo, mysql, docker, rabbit-mq, will these services run in the background? even if I don't open wsl ubuntu ? I'm just worried that services running are eating up my resources, but I'd be happy if they weren't running in the background.

:)

 

Systemd support is now available in WSL

Many popular distributions run systemd by default, such as Ubuntu, Debian and more. This change means that WSL will be even more similar to using your favorite Linux distros on a bare metal machine, and will let you use software that depends on systemd support.

A few examples of Linux applications that depend on systemd are:

• snap
  • A handy binary that allows you to install and manage software inside Ubuntu.
  • Try running: snap install spotify or snap install postman
• microk8s
  • Get Kubernetes running locally on your system quickly.
  • Try the getting started tutorial
• systemctl
  • A tool that’s part of systemd, interact with services on your Linux machine
  • Try systemctl list-units --type=service to see which services are available and their status

How is this change possible in WSL?

Supporting systemd required changes to the WSL architecture. As systemd requires PID 1, the WSL init process started within the Linux distribution becomes a child process of the systemd. Because the WSL init process is responsible for providing the infrastructure for communication between the Linux and Windows components, changing this hierarchy required rethinking some of the assumptions made with the WSL init process. Additional modifications had to be made to ensure a clean shutdown (as that shutdown is controlled by systemd now) and to have compatibility with WSLg, It is also important to note that with these change, systemd services will NOT keep your WSL instance alive. Your WSL instance will stay alive in the same way it did before, which you can read more about here.

Given that this changes how WSL behaves when booting up, we wanted to be careful about applying this to user’s already existing WSL distros. So currently you need to opt-in to enable systemd for a specific WSL distro, and we will monitor feedback and investigate making this behavior by default in the future.

How can you get systemd on your machine?

To get started, you will need to do these two things: – Ensure you are running the right version of WSL: Version 0.67.6 and above – Set the systemd flag set in your WSL distro settings

Ensuring you are on the right WSL version

This change is only available in the Microsoft Store version of WSL version 0.67.6 and higher. You can check your version number by running wsl --version. If that command fails then you are running the in-Windows version of WSL and need to upgrade to the Store version.

This version of WSL is now available in the Microsoft Store to users on Windows Insiders build for initial testing, and then after a few weeks we will make it available to all users to ensure quality. You can run wsl --update to check for any WSL updates.

If you are not on Windows Insiders and want to use it immediately, you can download the latest release from the WSL release page.

Set the systemd flag set in your WSL distro settings

You will need to edit the wsl.conf file to ensure systemd starts up on boot.

Add these lines to the /etc/wsl.conf (note you will need to run your editor with sudo privileges, e.g: sudo nano /etc/wsl.conf):

Code:

And close out of the nano editor using CTRL+O to save and CTRL+X to exit.

Final steps

With the above steps done, close your WSL distro Windows and run wsl.exe --shutdown from PowerShell to restart your WSL instances. Upon launch you should have systemd running. You can check this with the command systemctl list-unit-files --type=service which should show your services’ status.

Acknowledgements and Feedback!

Thank you to the Canonical team for working with us to deliver this feature! Check out Canonical’s blog post here. For any technical issues please file them on the Microsoft/WSL Github repo. You can follow up with WSL team members, or with me on Twitter. Lastly, learn more about WSL, including how to set up common development tools like Git, VS Code, Docker containers, databases, GPU acceleration for machine learning, and more, by visiting the WSL documentation.
Source: https://devblogs.microsoft.com/comma...ilable-in-wsl/

Microsoft Store: https://www.elevenforum.com/t/instal...indows-11.377/

 

Gaming Lag and Background Intelligence Transfer Service (BITS)

Let's try disabling the Background Intelligent Transfer Service (BITS) via Command Prompt by following the steps below:

• Open Command Prompt.
• Run/type msconfig.
• Click on Services tab.
• Remove check mark on Background Intelligent Transfer Service.
• Click on Apply.
• Restart your computer.

Get back to us if you need further assistance.

 

Error code: Wsl/Service/CreateInstance/MountVhd/ERROR FILE NOT FOUND

Hey there, Muthu Raman,

Welcome to Microsoft community.

It seems like you're having trouble with WSL and mounting your old C drive files after reinstalling OpenSUSE Tumbleweed. Here's a step-by-step guide to help you troubleshoot the issue:

1. First, ensure that WSL is enabled on your system. You can do this by running the following command in an elevated (administrator) PowerShell:
   
   
2. Make sure the OpenSUSE Tumbleweed distribution is set as the default WSL distribution. You can do this by running:
   
   
3. Check the list of installed WSL distributions using the following command:
   
   
   Look for the OpenSUSE Tumbleweed distribution in the list and make a note of its name.
   
4. If the distribution is not set to use WSL 2, update its version by running:
   
   
   Replace <DistroName> with the name of your OpenSUSE Tumbleweed distribution from the list.
   
5. Since you've reinstalled the OpenSUSE Tumbleweed distribution, your old mount point might have been removed. To remount your C drive, you can use the following command in your WSL terminal:
   
   

Unfortunately WSL is not supported on the Microsoft Answers forum. If the steps above do not solve your problem, it is more suitable for publishing on Microsoft Learn, you can click on "Ask a question", there are experts who can provide more professional solutions in that place.

Here is a link: Windows 10 - Microsoft Q&A to the forum where you can raise specific scenarios and share your idea to help solve the problem.





I'll leave that question open in case one of our amazing volunteers has ideas for you.

Thanks for your great understanding and support!

Have a nice day and stay safe!

Best regards,

Olivia | Microsoft Community Support Specialist