microsoft / microsoft/WSL

WSL 2 Loss of resource control settings compared to old WSL , on Docker Desktop

Open
#9,537 0 comments 0 reactions 0 assignees View on GitHub
feature
Dominant language
C++
Stars
33.7k
Forks
1.8k
Avg merge
3d 17h
Merged PRs (30d)
116

Description

**WSL --> WSL 2 User hope that upgrades cause things to improve!**
in Docker Desktop: goto Settings--> Resources --> Advanced
- Since it is NOT integrating with WSL 2 it outputs not correctly spelt and unhelpful text instead as follows:-

You are using the WSL 2 backend, so resource limits are managed by Windows.
You can configure limits on the memory, CPU, and swap size allocated to WSL 2 in a [.wslconfig file](https://github.com/microsoft/WSL/issues/new?assignees=&labels=feature&template=feature_request.md&title=).

(Note the above is a link out from Docker Desktop to a further very unhelpful web page, leaving the users Puzzled.)

**Solution Plugin or Collaboration with Docker Desktop Team**
For a WSL 2 full exact clear GUI integration, you will need to collaborate with the Docker Desktop team on that AND
ask for the web page (link above) to also be improved. You are encouraged to give them a detailed design with a Gui Layout.
If this is possible with a Docker Desktop plugin that you (Microsoft) do that may be best --- if plugins exist for setups.

Linux under Microsoft is the perfect definition of the word *oxymoron* both from the perspective of Linux fans as well as Microsoft fans. To be clear about the English language: *"oxymoron"* is **not** a rude word, it never was and never will be!

**Screenshot**
![docker_resources](https://user-images.githubusercontent.com/117369843/214655558-d954cc4c-9ebc-494e-aa66-bb672470366e.png)

Contributor guide

Open the contributing guide

Research direction

The issue points to Docker Desktop Settings → Resources → Advanced and an external .wslconfig feature-request link, not to a WSL file or test. Start by reviewing the WSL 2 resource-limit integration and linked Docker Desktop workflow; done would require an agreed GUI integration and clearer guidance, which this issue does not specify.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
devops, operating-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.