Ever Since I updated Docker, my dependency-track instance abends on startup

My team runs a local Docker instance on one of its scratch PCs, and for the last year and a half, I’ve been using it to do SBOM analysis using Dependency-Track . Last week, I successfully ran an analysis and captured it for my team. Then I noticed a button in the upper left corner inviting me to upgrade to the latest version of Docker. I clicked the button, and upgraded to the latest, and this is where my trouble with Dependency-Track started. Ever since I installed that new Docker instance, Dependency-Track says in the log, “Dependency-Track requires a minimum of 4GB RAM (heap). Cannot continue.” I’ve even tried uninstalling the new Docker, and reinstalling the old Docker (from 8/2023) using the MSI installer I originally used. I still get this message, and the page won’t open from the browser. I’ve also tried removing Dependency-Track and reinstalling it using this command I originally used: docker run -d -m 8192m -p 8080:8080 --name dependency-track -v dependency-track:/data dependencytrack/bundled

Can anyone tell me what I’m missing here?

Is it possible that you previously installed Docker Desktop using a different backend (HyperV or WSL2) and lost your old limit? With the WSL2 backend, you can configure the memory limit in WSL2

With the HyperV backend, I guess it should be in Docker Desktop under Resources.

I don’t remember much about setting up my Docker instance, but I still have a screen shot of a message I got back then saying my WSL version was too low, and instructing me to type wsl --update, which I gather I did, in order to get the thing running. I’m going to try to find a .wslconfig or wsl.conf file and see if modifying it helps.

Thanks!

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.