If you're running SonarQube (or anything CPU- and memory-hungry) inside Docker Desktop on Windows and the scans feel like they're running through molasses, your .wslconfig is probably the first place to look. That was my story this week, and the fix was satisfyingly small. Here's the whole journey, end to end, including the gotchas. Symptom: scans stall, fans spin, nothing finishes I was running a SonarQube scan on a mid-sized codebase inside a Docker container on Windows. The scan would chug along for a few minutes, then either crawl or stall outright. Nothing in the SonarQube logs screamed "out of memory" but the host felt fine, so it wasn't a Windows-side resource problem. Diagnosis: ask Docker what it actually has Docker Desktop on Windows runs everything inside a WSL 2 VM called docker-desktop . Whatever resources you've given that VM is the ceiling for every container you run.…