Jurak Posted June 5, 2021 Share Posted June 5, 2021 I need some help in finding what I have set up wrong. Diagnostics attached. plexserver-diagnostics-20210605-0931.zip Quote Link to comment
trurl Posted June 5, 2021 Share Posted June 5, 2021 There are a number of things about your docker configuration that are less than ideal. Your appdata and system shares have files on the array. This will cause array disks to stay spunup since these files are always open, and it will impact docker/VM performance due to slower parity. But it is not the reason for filling rootfs. Why have you given 50G to docker.img? Have you had problems filling it? 20G should be more than enough. The usual cause of filling docker.img is an application writing to a path that isn't mapped. Linux is case-sensitive, so each application must only specify paths that correspond to container paths in the mappings, and must match upper/lower case. The usual reason for a docker to fill rootfs is specifying a host path that isn't actual storage. Any host path that isn't a subfolder of /mnt is a path in rootfs. Quote Link to comment
Jurak Posted June 5, 2021 Author Share Posted June 5, 2021 1 minute ago, trurl said: The usual reason for a docker to fill rootfs is specifying a host path that isn't actual storage. Any host path that isn't a subfolder of /mnt is a path in rootfs. I will go through my docker configs and check this. Thanks Quote Link to comment
Recommended Posts
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.