May 1, 20224 yr Everything was running pretty smoothly until recently. I got a warning from Unraid about my Docker image file running out of space, so I stopped the docker service, and upgraded it to 100GB. I've had this machine for a long time, so it was still using the btrfs image. Ever since then, I am constantly restarting my Jellyfin image (most used image so when it goes down I know about it pretty quick). I have since switched to the xfs Docker image file, and after rebuilding all of my dockers, it's still doing the same thing. Can someone take a look and tell me what could be going on? It almost seems like a CPU utilization thing? But when I look at htop it doesn't look like this at all... It shows pretty low CPU utilization. (Half of these are reserved for my VM that's turned off for this screenshot) gunhaver-diagnostics-20220501-1913.zip Edited May 1, 20224 yr by m0ngr31
May 1, 20224 yr 20G is usually plenty for docker.img, maybe 30G depending on which and how many containers. No way should you ever need 100G. Increasing the size won't fix the reason it is filling, it will only make it take longer to fill. The usual cause of filling docker.img is an application writing to a path that isn't mapped to host storage. Syslog shows processes getting killed due to Out-Of-Memory.
May 1, 20224 yr https://wiki.unraid.net/Manual/Docker_Management#Re-Create_the_Docker_image_file https://wiki.unraid.net/Manual/Docker_Management#Re-Installing_Docker_Applications
May 1, 20224 yr Author 27 minutes ago, trurl said: https://wiki.unraid.net/Manual/Docker_Management#Re-Create_the_Docker_image_file https://wiki.unraid.net/Manual/Docker_Management#Re-Installing_Docker_Applications I did this already today. I'm struggling to figure out why it thinks it's running out of RAM when htop doesn't show it using more than 15GB.
May 2, 20224 yr Author 17 hours ago, trurl said: 20G is usually plenty for docker.img, maybe 30G depending on which and how many containers. No way should you ever need 100G. Increasing the size won't fix the reason it is filling, it will only make it take longer to fill. The usual cause of filling docker.img is an application writing to a path that isn't mapped to host storage. Syslog shows processes getting killed due to Out-Of-Memory. It was giving me the warning message when I had a 75GB image, so it fixed that issue at least. I am running a lot of dockers, but I'm trying to figure out what is causing everything to run out of memory.
May 2, 20224 yr 51 minutes ago, m0ngr31 said: It was giving me the warning message when I had a 75GB image, so it fixed that issue at least 18 hours ago, trurl said: Increasing the size won't fix the reason it is filling, it will only make it take longer to fill. Go to Dockers page, click Container Size button at bottom, and post a screenshot.
May 2, 20224 yr Author 17 minutes ago, trurl said: Go to Dockers page, click Container Size button at bottom, and post a screenshot. I haven't put back all the containers yet, and I'm not too concerned about the docker image, just trying to figure out what is taking up all my RAM and crashing everything. Edited May 2, 20224 yr by m0ngr31
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.