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 threadGlyph
@mcc I think that windows is the only platform that runs the containers in separate VMs by default, so on most other configurations you get a single VM whose memory you can tune how you like; per-container resource constraints are tunable at `docker run` time https://docs.docker.com/config/containers/resource_constraints/
"Runtime options with Memory, CPUs, and GPUs"

"Specify the runtime options for a container"

Docker Documentation
Aug 5, 2023 at 10:32pmWeb