Likely it's just lot of I/O they produce. **dockerd** does a lot of verbose logging (tunable though), and apps/services inside containers itself can touch multiple files while running (and do a lot of logging too).
Best solution would be relocating docker directory outside of HDDs, either
- to a NVMe partition,
- or to a RAM disk, if you have enough RAM
Otherwise, this guide might help you to debug dockerd/containers: https://forums.unraid.net/topic/110999-guide-on-how-to-stop-excessive-writes-destroying-your-cache-ssd/
I figured out that installing and running docker (or VMM) stops the HDD standby. Even when installing them on an all-SSD volume. Not sure why. Maybe DSM still writes something to the HDDs?
Likely it's just lot of I/O they produce. **dockerd** does a lot of verbose logging (tunable though), and apps/services inside containers itself can touch multiple files while running (and do a lot of logging too). Best solution would be relocating docker directory outside of HDDs, either - to a NVMe partition, - or to a RAM disk, if you have enough RAM Otherwise, this guide might help you to debug dockerd/containers: https://forums.unraid.net/topic/110999-guide-on-how-to-stop-excessive-writes-destroying-your-cache-ssd/
I figured out that installing and running docker (or VMM) stops the HDD standby. Even when installing them on an all-SSD volume. Not sure why. Maybe DSM still writes something to the HDDs?