I have been running a pi node with a Beelink Ser7 mini pc since October 2024. For the last month or so, the docker has been using all of the RAM. This causes the PC to freeze or shut down. Even if I turn off the node and docker, or even turn off the PC, when I turn on the PC again, the PC starts with 100% RAM used. My only solution is to turn off the PC with the power button. Then it starts normally, and when I run the node and docker, I get to the same situation again within 1 day. I have 32 gb ddr5 ram and I am using win 11. Does anyone know a solution to this?
Hi
Iâve never used them but you should know itâs possible to add restrictions to a container, see Resource constraints | Docker Docs
Otherwise no idea what is the cause of your problemâŠ
1 Like
What is âthe dockerâ? Do you mean container? Or the Docker Docker Desktop itself? A container is not âa dockerâ.
If a container is using too much RAM, you need to debug the application running in it. If the Docker Desktop is using too much RAM, then you can try to find out what the daemon does and log for system logs for example.
Note that Docker Desktop is not for running long. It is only for development and it was reported by many users that when running it for long, it uses more resources and can even crash sometimes. So use it for development and if you want to run Docker constantly, create a virtual machine (on Windows) to run a Linux OS and install Docker CE. Although 1 day should not be too long indeed.
By the way I recently noticed that my MacBook became hot pretty quickly after starting Docker Desktop and I had to realize a Docker Desktop extension must have created a container ever time I started Docker Desktop, so I had to disable the extension.
1 Like
Thanks for your answers. Sorry for not explaining my problem properly, I am very new to docker and I only run it 24/7 for the pi node. I only have 2 containers and one is always active. I also added photos of the programs that use ram. Please excuse me if I have given incomplete information or if I have not explained my problem properly.
Sorry for the late response, but I donât really know what to add to the topic. It is hard to see the photos. A screenshot would have been better, but I see that WSL and the docker backend uses lots of memory together. Iâm not entirely sure what could increase the memory requirement right after starting the machine. At least if I understood correctly, it started right after starting the machine and Docker.
You can try to search for similar issues on GitHub if you havenât solved it yet
1 Like