[Personal memo] A small story about CPUs settings of Docker Desktop for Windows

I referred to this. Docker Desktop WSL 2 Backend — Docker-docs-ja 19.03 ... Try Docker environment on Windows-Qiita Docker Desktop for Windows (reference translation) --Qiita

• This article is for Docker Desktop Community 2.3.7.0 (Windows) or earlier.

My environment is as follows. Microsoft Windows [Version 10.0.19041.508] Windows 10 Pro version 2004 64bit Intel Core i5-3340M 2.70GHz RAM 16GB Fujitsu LIFEBOOK P772/G

Information before VScode Version: 1.49.1 (user setup)

• As I confirmed today, the CPU usage was stable in the single digit range even when Docker Desktop for Windows was started with the "VS Code Remote Development" extension enabled in VS Code.

Windows Subsystem for Linux Release Notes The above site says, "Adjust the default memory allocation for the WSL2 VM to be 50% or 8 GB of host memory, whichever is less," so that may have helped. .. Previously, when I enabled Remote Development, an extension of VS Code, with WSL2 enabled, there was a phenomenon that the CPU usage remained close to 100%. At that time, when I tried to reduce the CPU allocation rate of WSL2, I noticed that the item of CPUs was not found in the Resources tab. Therefore, I would like to keep it as a memorandum.

Conclusion

It seems to be whether or not to check "Use the WSL 2 based engine" on the General tab. WSL2 seems to allocate resources dynamically, so I think that there is no need to configure it.

screenshot

When "Use the WSL 2 based engine" is checked

• Proxies and Network items on the Resources tab do not seem to change.

If "Use the WSL 2 based engine" is not checked

• There was a CPUs setting item in Advanced on the Resources tab.