Amino

I ended up using --memory caps and it seems to have stopped my issue, now when a docker container starts getting full it ends up clearing the ram used going back to an almost fresh restart state.

I've started playing around with docker containers in Unraid and have a few I leave up all the time like plex. I've noticed that the longer their active the more memory usage keeps increasing. Is this normal for Unraid to have to restart docker containers daily to keep ram usage down? The main one for me seems to be plex and it continues to grow when I'm adding new content into the library. Transcoding through ram always takes a few G then drops back down but fetching data seems to stay in ram. Filezilla also seems to end up quite high after searching though FTP site and downloading. I feel like I might be missing something as I've ran docker container for plex before but its never gotten as high as it has been for Unraid i had it well over 40gb in ram usage in just a day of adding new content to my library.

Anyone able to tell me why a mounted device would keep mounting into read only while read only is unchecked: Sep 28 10:46:45 HomeLab unassigned.devices: Mount cmd: /sbin/mount -t 'ntfs' -o rw,relatime,nodev,nosuid,nls=utf8,umask=000 '/dev/sdc2' '/mnt/disks/anime' Sep 28 10:46:47 HomeLab ntfs-3g[31567]: Mounted /dev/sdc2 (Read-Only, label "Plex", NTFS 3.1) I ended up finding the error out side of the mounting logs. Sep 28 11:02:00 HomeLab unassigned.devices: Mount warning: The disk contains an unclean file system (0, 0). Metadata kept in Windows cache, refused to mount. Falling back to read-only mount because the NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting.) Could not mount read-write, trying read-only If anyone else ends up having this issue you can simply put it into a windows machine and safely eject it and it will clear up the issue.