My SonarQube scans were crawling; turns out Docker on WSL 2 only had 1 CPU and 1 GB of RAM

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 al