Just got this error two nights ago. Got the same error last night. Any guidance? It looks like some erros are due to me not upgrading from 6.5.3, but I don't know if that's mandatory.

 

sophos-diagnostics-20190117-1726.zip

Since you have an oversized docker image, and also an Unassigned Device mounted, I wonder if you don't have one or more of your dockers misconfigured.

 

It is very unlikely to ever need even 20G for the docker image. People who make theirs larger are often trying to solve a problem with docker image filling up. Making it larger won't make the problem go away, it will just make it take longer to fill.

 

The typical way a container will fill docker image is if the application isn't writing to mapped storage. Any path in the application that doesn't correspond to a path within some volume mapping will write into the docker image, filling it up.

 

And the typical way a container will fill memory is by mapping a path that isn't to Unraid storage. Since the Unraid OS and its root filesystem are in RAM, if you map a docker volume to something other than the user shares or one of the disks then the container will write to RAM.

 

And the reason I mentioned the Unassigned Device is because if you map a volume to an Unassigned Device, but that device happens to be not mounted, then that path will be in RAM also.

Thanks so much for spending the time to respond.

 

I have tried to troubleshoot the docker image sizing previously but did not identify any dockers taking up huge amounts of space. It seems to be stable at its current size.

 

Since my out of memory errors seemed to be concomitant with the “find problems” plugin, and since these errors were related to the Unraid version not being up to date, I said a quick prayer and updated to 6.6.6 last night. Everything seems to be fine, and I did not get an error message/out of memory email last night.

 

If I get more memory errors in the future, I’ll post back in this thread.

 

Again, thanks!