guniv

As long as you're above whatever is in the docs you should be fine. I have never had an issue across four systems.

Would you mind posting a screenshot of your full Docker config for the container just to double check? Like this (this is mine, will be slightly different):

Not that I know of. I would be surprised if there was. I am guessing that displaying the CC page in a browser takes a lot of resources on the system showing the page. This is veering into general support for CC and I'm mainly here to help with Docker specific issues. If you want additional help with setup or reporting bugs I would join the discussion on the Discord.

If it's a device being passed through to a VM then Docker/Unraid/CoolerControl would not also be able to access it. That would be something you'd set up in the VM. I know the Windows program FanControl is very very similar.

There is not a way to have CC send notifications to Unraid's notification system.

Yeah, driver support can be iffy and some motherboard manufacturers tend to have better support for this than others. If you manage to get anything working, and if you think the docs should be updated to reflect it, please let us know!

Did you read through the setup guide included in the container's description? You need to go mount your fans to the container. It sounds like you only have hwmon mounted at the moment, which is included in the template as read-only.

Yep, in the app. The Docker container.

You can look at the logs in the container by clicking the CoolerControl icon/logo in the top left.

Important update! The CoolerControl devs are now maintaining an official Docker container so I will be deprecating mine. I have updated the template, repo, etc to reflect this, and added a warning in the logs. If you are already running the container you can update the repo to coolercontrol/coolercontrold:latest and it should just keep on working! Thanks for everyone's support!

Please read this guide: https://github.com/guniv/CoolerControl-Docker/blob/main/setup.md You need to run some commands to enable HDD temperature.

My best guess here is that perhaps the CoolerControl container is starting before the script that enables drivetemp has a chance to start. Maybe one way around this would be to uncheck "Autostart" for the container in the Docker tab of Unraid and add this line to the drivetemp script: docker start CoolerControl So that will start the container after drivetemp has been enabled.

Just chiming in here, I see the issue was identified as coming from enabling drivetemp. Another CoolerControl user had essentially the same issue and identified that in versions of Unraid earlier than 7.0.1 there was a kernel bug that caused issues with drivetemp and spun down drives: https://lore.kernel.org/linux-cve-announce/2025012131-CVE-2025-21656-b967@gregkh/T/#u I've updated the CoolerControl docs to warn users about this issue and sorry you ran into this!

Yeah, if you are passing through the it8613 directory (as gone over in the setup guide) and it's still throwing this error you may need to run the container privileged.

I edited the CA template earlier today to use an image from Docker Hub instead of from GitHub which I guess on CA's end makes it think it's a brand new app. You can update your repository on your container and it should mark it as installed again on CA, but I will continue to update the GitHub image and it shouldn't matter to existing users!

Unfortunately this sounds like an issue with CoolerControl specifically and not the Docker container so I'll have to point you to them to ask for support if you still think it is CoolerControl causing the problem. However, I can say that I personally have not noticed CoolerControl causing my drives to spin back up after being slept and I haven't heard other reports of this so far (although there are temp reporting issues with spun down drives).

Thanks! I am writing new documentation now on this. In short the way the script works won't recognize coolercontrol as "used by a docker container" so I've edited the script to carve out a coolercontrol exception: https://github.com/guniv/CoolerControl-Docker/blob/main/tutorial/nvidia_power.sh I didn't catch this because I always have something on my server's GPU so thanks for reporting.

Can you share what the log shows for your Nvidia powersave script? I also use this script and have not encountered this issue, and this is what I get when I run the script: Listing NVIDIA Graphics Cards in your server... GPU 0: NVIDIA GeForce GTX 1070 (UUID: GPU-87c9b28c-e03f-b8fe-ea22-2ef8621b71c0) GPU 1: NVIDIA GeForce GTX 980 (UUID: GPU-b238369c-709f-7a8f-8efb-550113bb6937) Initial Power Usage and State -------------------------------------------- GPU 0 -- NVIDIA GeForce GTX 1070 Power Usage -- 9.24 W Power State -- P8 -------------------------------------------- GPU 1 -- NVIDIA GeForce GTX 980 Power Usage -- 15.32 W Power State -- P8 -------------------------------------------- Checking for process termination eligibility... At least one GPU is being used by a Docker container. Will not terminate GPU-related processes.

What do you mean by stop? The container shuts down?

I honestly don't know if it will be, it's out of my knowledge level. When I was looking into it I think there's essentially a mismatch between how CoolerControl prefers to handle GPUs versus how the Unraid driver works, and CoolerControl also just mainly operates with the assumption it has full access to the system. If someone figures it out I'd be happy to update the documentation. I spent a lot of time trying to adjust the container itself or even adjust the stuff I was mounting to the container and had no luck.

I'd recommend deleting the files in the CoolerControl appdata folder that the container mounts so that it sets the config back to default and seeing if that fixes it.

Just to confirm: your settings look like this? And then my docker run command looks like this after:

Okay, I was incorrect about this! Running this on your server gives hwmon access to drive temperatures and they will show up in CoolerControl: sudo modprobe drivetemp So, you can set up a user script to run on first array start and CoolerControl should have no issue seeing the drive temps.

Thank you. I have updated the template to instead mount /sys/class/hwmon to the container which appears should work for both AMD and Intel. I have no idea how long it takes for Community Applications to use the new template, but for now anyone facing this issue can update their template manually:

For any of my AMD users: if you could get the container running by removing the hwmon mount and running the container privileged, and then showing me the locations listed here next to your CPU, that should help me figure out how to adjust the default template.