mccAug 5, 2023
Last year I had Docker briefly running on my Win10 machine, just long enough to verify it was working, then today I ran it and it said it can't run because of my BIOS settings. Is this surprising? Does this imply I changed my BIOS, possibly by accident, sometime in the last nine months? If I changed out my boot disk, might that have reset some BIOS settings?
Show threadmccAug 5, 2023
Follow up question: In my testing, it appeared that Docker Desktop for Windows reserved 2GB of RAM for each of its virtual machines (seemingly due to something about how WSL works). It was not 100% clear to me if this reserved RAM block could be swapped out but I assume not. Do Docker Desktop on Mac and Linux have a similar issue (IE that each VM hardwire-reserves a fixed amount of RAM regardless of how much it is using at any one moment?)
Show threadspinningmonkey

@mcc WSL2 will use up to 50% of your memory with it's default settings. Docker seems to escalate maxing out wsl memory usage.

You can limit this by creating a .wslconfig file in your user directory. Nice write up here by @willem_meints https://fizzylogic.nl/2023/01/05/how-to-configure-memory-limits-in-wsl2

How to configure memory limits in WSL2

One of the downsides to building machine learning models is that you need quite a bit of power in your machine. I've just upgraded my home desktop that I use for side projects and experiments to 64GB of memory because it was clearly no longer up to the task. However, when I booted up my WSL linux distro, it couldn't get more than 32GB of memory. Time to figure out how to fix that! In this quick post I'm showing you how you can limit or increase the memory available to your WSL2 distributions. Let's go!

Willem's Fizzy Logic
Aug 5, 2023 at 11:41pmWeb