I started my system as usual but my docker-desktop doesn't work, WSL doesn't respond to commands and there is a process called "Vmmem" using 25% of my memory. I have tried a bunch of thing but nothing seems to work.
Recently I was having trouble with my docker set up. I have one particular container that was "crashing" the docker. It was not throwing any exception but after some event (that I couldn't find out) all the other container where unreachable any attempt to stop/start another container would result on "Error: 500 failed to respond...". When this happens I usually just restart the system and everything works fine, but today it wasn't the case. I restarted and I noticed that I had the "Vmmem" process already running at 25% (it usually just reaches this point at the end of the day), the docker desktop could not start the docker backend and when I tried running wsl -l -v
I got no response. I can use some docker commands like docker -v
but the docker compose up
doesn't work at all.
net start/stop <service>
(it gives a response but didn't solve the problem)wsl -t Ubuntu
(got no response from wsl)I managed to finally install the Docker desktop 4.16 but the problem continues, system starts with 25% Vmmem memory usage and docker desktop is not able to initiate backend.
Steps that I did to be able to stop "Vmmem" process and install docker desktop again:
to this point the "Vmmem" problem was gone
hypervisorlaunchtype
Maybe some steps listed here are redundant but that is what I did. hope it helps if other people is passing through the same problem