27-08-2022, 02:22
I am running Minimserver on my Synology NAS - and I am running three instances (to keep DSF files separate from my mp3 or m4a files):
- The regular package for Synology (MinimServer 2.1.2 update 218)
- Two Docker containers with the minimworld/minimserver docker image from hub.docker.com - which also seems to be version 2.1.2 update 218.
With only the Synology package version of Minimserver running, everything is fine: After a certain amount of time, all activity on the NAS devices seizes and my disks and NAS go to sleep.
This changes the moment I start one of the docker containers with Minimserver inside: Now I see write activity on my drives starting fairly precisely every 30 seconds - and as a result, my NAS cannot go to sleep anymore.
I have had similar issues with other containers - which were running Docker "health check", which also keeps writing to disk - but the write activity was coming from a different process than in the case of Minimserver's containers.
Can you help figuring out why a Minimserver container keeps writing to disk, whereas the Synology package installation does not?
Thank you!
- The regular package for Synology (MinimServer 2.1.2 update 218)
- Two Docker containers with the minimworld/minimserver docker image from hub.docker.com - which also seems to be version 2.1.2 update 218.
With only the Synology package version of Minimserver running, everything is fine: After a certain amount of time, all activity on the NAS devices seizes and my disks and NAS go to sleep.
This changes the moment I start one of the docker containers with Minimserver inside: Now I see write activity on my drives starting fairly precisely every 30 seconds - and as a result, my NAS cannot go to sleep anymore.
I have had similar issues with other containers - which were running Docker "health check", which also keeps writing to disk - but the write activity was coming from a different process than in the case of Minimserver's containers.
Can you help figuring out why a Minimserver container keeps writing to disk, whereas the Synology package installation does not?
Thank you!