This thread is for support for CoolerControl. I wanted to set this up to use with my Unraid server so I threw a container together and the CC devs later released an official container. I'll do my best to help others here, but many issues may be hardware specific or may be with CoolerControl, which I am not involved with developing.

This is the CoolerControl repo: https://gitlab.com/coolercontrol/coolercontrol

You can view a guide on how to install this in Unraid here: https://docs.coolercontrol.org/installation/unraid.html

Edited August 4, 2025Aug 4 by guniv
Changing to official CC resources

Just what I've been looking for!

 

Easiest way to get this into Unraid for linux novice? I'm getting "manifest unknown" when trying to pull via gui or terminal...

5 minutes ago, Monkey50 said:

Just what I've been looking for!

 

Easiest way to get this into Unraid for linux novice? I'm getting "manifest unknown" when trying to pull via gui or terminal...

Fixed, sorry about that, give it another shot.

Trying to install the image fails, giving me:

 

docker: Error response from daemon: error while creating mount source path '/sys/devices/platform/coretemp.0/hwmon': mkdir /sys/devices/platform/coretemp.0: operation not permitted.

 

Trying to install as privileged, btw.

 

any ideas?

I don't think i've ever had such a frustrating experience installing an app...

Install all fine, but as i log in, I'm asked for a password, it says use the default one. So i go on the hunt for it, half of the gitlab links end up at 404, documentation hasn't got it, install notes does not list it.

i have the same problem

docker: Error response from daemon: error while creating mount source path '/sys/devices/platform/coretemp.0/hwmon': mkdir /sys/devices/platform/coretemp.0: operation not permitted.

Hi,

 

Thanks for the image. It worked for me out of the box, but it didn´t register de HDD temps (the SDDs are there). Is there any way to get them registered in the app?

I'm also getting same error relating to /sys/devices/platform/coretemp.0/hwmon - that path doesn't exist on my unraid server - is there a dependency on something else?

 

OK, I figured it out. I edited (more settings) container and host path (by clicking the edit button to see the expanded dialogue box) to set both to:

/sys/devices/platform/it87.2608/hwmon

I have the ITE IT87 drivers installed.

Edited April 1, 20251 yr by MatthewD

6 hours ago, Krakout said:

Trying to install the image fails, giving me:

 

docker: Error response from daemon: error while creating mount source path '/sys/devices/platform/coretemp.0/hwmon': mkdir /sys/devices/platform/coretemp.0: operation not permitted.

 

Trying to install as privileged, btw.

 

any ideas?

 

4 hours ago, Lordbye said:

i have the same problem

docker: Error response from daemon: error while creating mount source path '/sys/devices/platform/coretemp.0/hwmon': mkdir /sys/devices/platform/coretemp.0: operation not permitted.

Can I ask what your system specs are for each of you? I'm wondering if this is an AMD vs Intel thing or something like that. I just checked on one of my systems to make sure it wasn't because a plugin I had was adding a dependency, but it still works fine after I removed a bunch of plugins that I thought might be the cause. For the record both of my systems at home are Intel based (14600k and N305).

In any case, you should be able to remove the "hwmon" mount under "Show more settings" and things should probably work after that. I'd like to get to the bottom of this if possible but I may just need to remove that volume from the default template.

2 hours ago, MatthewD said:

I'm also getting same error relating to /sys/devices/platform/coretemp.0/hwmon - that path doesn't exist on my unraid server - is there a dependency on something else?

 

OK, I figured it out. I edited (more settings) container and host path (by clicking the edit button to see the expanded dialogue box) to set both to:

/sys/devices/platform/it87.2608/hwmon

I have the ITE IT87 drivers installed.

On my systems I had both the coretemp folder mounted (as read only) and the it87 folder mounted (as read write, for fan control) and it was working okay, but glad you figured it out.

Edited April 1, 20251 yr by guniv

3 hours ago, wide-ranging-lecture5669 said:

Hi,

 

Thanks for the image. It worked for me out of the box, but it didn´t register de HDD temps (the SDDs are there). Is there any way to get them registered in the app?

As far as I know CoolerControl does not support HDD temps unfortunately. I recommend using the Dynamix Auto Fan Control plugin to assign one of your fans to cooling the HDDs. If you want this support you would have to ask the CoolerControl developers.

5 hours ago, MegaBlindy said:

I don't think i've ever had such a frustrating experience installing an app...

Install all fine, but as i log in, I'm asked for a password, it says use the default one. So i go on the hunt for it, half of the gitlab links end up at 404, documentation hasn't got it, install notes does not list it.

I'm not sure why you would be getting a password request for this as I've never encountered a login screen on CoolerControl. I did find this page in their documentation: https://docs.coolercontrol.org/wiki/access-protection.html

9 minutes ago, guniv said:

 

Can I ask what your system specs are for each of you? I'm wondering if this is an AMD vs Intel thing or something like that. I just checked on one of my systems to make sure it wasn't because a plugin I had was adding a dependency, but it still works fine after I removed a bunch of plugins that I thought might be the cause. For the record both of my systems at home are Intel based (14600k and N305).

In any case, you should be able to remove the "hwmon" mount under "Show more settings" and things should probably work after that. I'd like to get to the bottom of this if possible but I may just need to remove that volume from the default template.

AMD. Will try removing the mount in the morning and will report (I'm in Europe)

Just now, Krakout said:

AMD. Will try removing the mount in the morning and will report (I'm in Europe)

That's good to know, if the other users are using AMD that would confirm my suspicions. I think what I'll have to do in this case is find the appropriate read-only mount for AMD systems and then have the users select the correct one when setting up the template.

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.

 

I hope this helps , thank you for adding the app and the support.
 

Edited April 1, 20251 yr by SEK

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:

ecco il mio sistema

MyNas: 7.0.1 rilasciato • Case: Sharkoon 2Xu2 • MB: B550M DS3H AC • CPU: Ryzen 5 5600GT@ 3.60GHz • Dissipatore: upHere pk5 • PSU: Koolink Classi power 600W • RAM: 48GB (2x16GB + 2x8GB) DDR4 • Parità: 1 WB Red 4 TB • Archiviazione dati: 4 WB Red - 16TB totali (ZFS) • Scheda video: PNY QUADRO T400 2GB • Cache: 3 SSD 888 GB (totale) • Disco VM: 1 SSD 120GB kingstone.

 

Changing with new path (/sys/class/hwmon) is ok for me 

 

Edited April 1, 20251 yr by Lordbye
upodate

4 hours ago, guniv said:

As far as I know CoolerControl does not support HDD temps unfortunately. I recommend using the Dynamix Auto Fan Control plugin to assign one of your fans to cooling the HDDs. If you want this support you would have to ask the CoolerControl developers.

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.

Trying to add the nvidia support and the container fails to start with a complaint from docker:

docker run
  -d
  --name='CoolerControl'
  --net='bridge'
  --pids-limit 2048
  --privileged=true
  -e TZ="America/Los_Angeles"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="pinkfloyd.local"
  -e HOST_CONTAINERNAME="CoolerControl"
  -e 'CA_TS_FALLBACK_DIR'='/etc/coolercontrol'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:11987]/'
  -l net.unraid.docker.icon='https://gitlab.com/coolercontrol/coolercontrol/-/raw/main/coolercontrol/icons/icon.png'
  -p '11987:11987/tcp'
  -v '/mnt/user/appdata/coolercontrol':'/etc/coolercontrol':'rw'
  -v '/sys/class/hwmon':'/sys/class/hwmon':'ro' '--runtime=nvidia
  --gpus=all' 'ghcr.io/guniv/coolercontrol-docker'
docker: Error response from daemon: unknown or invalid runtime name: nvidia --gpus=all.
See 'docker run --help'.

This is from following the instructions on how to activate the functionality. Without it the app starts.

 

I tried the nvidia support again, this time with double-quots around all the flags (ie. "--runtime=nvidia --gpus=all") and got a similar message, but I noticed that the container image name is appearing after the additional args.

docker run
  -d
  --name='CoolerControl'
  --net='bridge'
  --pids-limit 2048
  --privileged=true
  -e TZ="America/Los_Angeles"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="pinkfloyd.local"
  -e HOST_CONTAINERNAME="CoolerControl"
  -e 'CA_TS_FALLBACK_DIR'='/etc/coolercontrol'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:11987]/'
  -l net.unraid.docker.icon='https://gitlab.com/coolercontrol/coolercontrol/-/raw/main/coolercontrol/icons/icon.png'
  -p '11987:11987/tcp'
  -v '/mnt/user/appdata/coolercontrol':'/etc/coolercontrol':'rw'
  -v '/sys/class/hwmon':'/sys/class/hwmon':'ro' "--runtime=nvidia
  --gpus=all" 'ghcr.io/guniv/coolercontrol-docker'
docker: Error response from daemon: unknown or invalid runtime name: nvidia --gpus=all.
See 'docker run --help'.

 

So I'm thinking that 'Extra Values' is inserting in the wrong order. Should be on the end of the command.

 

BTW, when the container fails to start, the container disappears from the webgui and from 'docker container ls --all'. Even if you successfully started it previously without the nvidia args, as soon as you apply them...the container disappears! Neat trick, huh?

Edited April 2, 20251 yr by ghstridr
Adding further data and thoughts

1 hour ago, ghstridr said:

Trying to add the nvidia support and the container fails to start with a complaint from docker:

docker run
  -d
  --name='CoolerControl'
  --net='bridge'
  --pids-limit 2048
  --privileged=true
  -e TZ="America/Los_Angeles"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="pinkfloyd.local"
  -e HOST_CONTAINERNAME="CoolerControl"
  -e 'CA_TS_FALLBACK_DIR'='/etc/coolercontrol'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:11987]/'
  -l net.unraid.docker.icon='https://gitlab.com/coolercontrol/coolercontrol/-/raw/main/coolercontrol/icons/icon.png'
  -p '11987:11987/tcp'
  -v '/mnt/user/appdata/coolercontrol':'/etc/coolercontrol':'rw'
  -v '/sys/class/hwmon':'/sys/class/hwmon':'ro' '--runtime=nvidia
  --gpus=all' 'ghcr.io/guniv/coolercontrol-docker'
docker: Error response from daemon: unknown or invalid runtime name: nvidia --gpus=all.
See 'docker run --help'.

This is from following the instructions on how to activate the functionality. Without it the app starts.

 

I tried the nvidia support again, this time with double-quots around all the flags (ie. "--runtime=nvidia --gpus=all") and got a similar message, but I noticed that the container image name is appearing after the additional args.

docker run
  -d
  --name='CoolerControl'
  --net='bridge'
  --pids-limit 2048
  --privileged=true
  -e TZ="America/Los_Angeles"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="pinkfloyd.local"
  -e HOST_CONTAINERNAME="CoolerControl"
  -e 'CA_TS_FALLBACK_DIR'='/etc/coolercontrol'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:11987]/'
  -l net.unraid.docker.icon='https://gitlab.com/coolercontrol/coolercontrol/-/raw/main/coolercontrol/icons/icon.png'
  -p '11987:11987/tcp'
  -v '/mnt/user/appdata/coolercontrol':'/etc/coolercontrol':'rw'
  -v '/sys/class/hwmon':'/sys/class/hwmon':'ro' "--runtime=nvidia
  --gpus=all" 'ghcr.io/guniv/coolercontrol-docker'
docker: Error response from daemon: unknown or invalid runtime name: nvidia --gpus=all.
See 'docker run --help'.

 

So I'm thinking that 'Extra Values' is inserting in the wrong order. Should be on the end of the command.

 

BTW, when the container fails to start, the container disappears from the webgui and from 'docker container ls --all'. Even if you successfully started it previously without the nvidia args, as soon as you apply them...the container disappears! Neat trick, huh?

Just to confirm: your settings look like this?

 

 

And then my docker run command looks like this after:

Edited April 2, 20251 yr by guniv

The update works on my setup perfectly

 

This is what I'm getting, when pressing f12 and deleting elements i can bypass this screen and start editing stuff, but every time i refresh the screen I need to fiddle around by deleting elements

1 minute ago, MegaBlindy said:

 

This is what I'm getting, when pressing f12 and deleting elements i can bypass this screen and start editing stuff, but every time i refresh the screen I need to fiddle around by deleting elements

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.

I replaced my tried-and-true fan control scripts with this docker earlier in the week and it's working great.

 

Will it ever be possible to control NVIDIA GPU fans without having to use privileged? Just curious if it's just a flat no it can't happen, or something that's on the roadmap. I know this is still new, and it's already the best Unraid fan controller by a large margin. I didn't even know this platform existed. Thanks for bringing it to Unraid!

Edited April 19, 20251 yr by anibis2