January 5, 20251 yr This started happening a couple days ago. I can no longer run Docker without it maxing out my CPU. Not sure what's going on. As soon as I reboot or start/restart Docker in Unraid, my CPU usage goes from <10% to 100%. Looking at htop it seems to be: /user/bin/dockred -p /vasr/run/dockerd.pid --log-opt max-size=500m max-file=1 --log-level=fatal --storage-driver=btrfs I have tired turning 1 docker on at a time, with mixed results. Sometimes it will be fine, then hours later decide to kick off. Other times, every docker startup will cause this. I have also tried restarting docker in settings and increasing the image disk size limit to 200GB. Looking for some guidance on what might be causing the issue. Thanks in advance! Unraid 6.12.14 (was also happening with 6.12.6) BK-diagnostics-20250105-1333.zip
January 6, 20251 yr I'm experiencing this as well. Did you figure something out? Stopping every single docker container does not help at all. Edit: Seems like my docker image got corrupted? I createad a new one and I'm resintalling everything and seems to be okay. Edit2: Now that I've reinstalled everything, seems to be back to the same thing, not as bad but 80% CPU usage now. Edited January 6, 20251 yr by pmcnano
January 6, 20251 yr Author Seems like this might be a more general issue users are experiencing. Anyone have any suggestions on resolution?
January 6, 20251 yr Well, I ended up recreating my docker.img. Reinstalled everything and I think there might've been one container causing issues so I just turned that one off. That being said I didn't have enough time to really check. Also before I started the high CPU usage was there even with all containers stopped. I also found some similar posts in the forum, so I'm going to say there's something off.
January 7, 20251 yr So I think I figured mine out...Do you happen to use Frigate NVR or any other NVR that uses object detection running under docker on your Unraid box? I do and I also live in the midwest. I hadn't put two and two together on my original reply until a friend of mine and I were talking about it. We had a blizzard this past weekend, and Frigate was having to run object detection on all that blowing snow. In fact, they list that right in their documentation. Quote The goal is to prevent object detection from running constantly for every small pixel change in the image. Windy days are still going to result in lots of motion being detected. So what was happening for me, is that Frigate was going crazy because of the weather. My issue was unrelated to Unraid. Edited January 7, 20251 yr by tyler.miranda
January 9, 20251 yr Author Frigate is not an issue for me either, not using it. I did the following....went from 100% CPU to 80% - 90% CPU usage. So not fixed but usable.... - Deleted docker.img - Re-installed each docker 1 by 1 There is something seriously wrong with Unraid. Definitely not performing normally. Would love if someone could take a look at diagnostic logs and help point these folks in the right direction for resolution.
February 24, 20251 yr I can report that I experience this as well. For me, this seems to be somewhat related to running TubeArchivist container - but it is definitely not the only culprit. This might be a coincidence, but what CPU is everyone running here? I am also on the 12600K like @Boy Kai - but on a different MB brand. I am on 7.0.0 but I experienced the same issue with 6.12.x Your logs are also probably filled with Feb 24 23:52:00 Tower php-fpm[15343]: [WARNING] [pool www] child 1375992 exited on signal 9 (SIGKILL) after 20.070926 seconds from start Edited February 24, 20251 yr by HumanTechDesign
February 28, 20251 yr On 2/24/2025 at 2:53 PM, HumanTechDesign said: Your logs are also probably filled with Feb 24 23:52:00 Tower php-fpm[15343]: [WARNING] [pool www] child 1375992 exited on signal 9 (SIGKILL) after 20.070926 seconds from start This issue has plagued me for sometime even before 7.0.0. I also have this line in my logs tons of times. I am running an 11th Gen Intel® Core™ i5-11400 @ 2.60GHz. Doesn't seem to have any rhyme or reason. Eventually it will go away or my machine will become unresponsive. I have standard plex/arr/krusader/pihole/qbit dockers. I ssh in and stop docker service and restart and issue goes away for a while. I also have a Cloudflare url pointing to it but not sure if related. I have thought about going to a directory instead of an Img for docker. Edited February 28, 20251 yr by spdelope
February 28, 20251 yr Community Expert In my experience, these errors can be the result of the server being close to exhausting the memory, GUI can become extremely slow, like 1 minute to open the dashboard, try limiting the memory for VMs/docker services, or adding a little more RAM.
March 1, 20251 yr On 2/28/2025 at 5:04 AM, spdelope said: This issue has plagued me for sometime even before 7.0.0. I also have this line in my logs tons of times. I am running an 11th Gen Intel® Core™ i5-11400 @ 2.60GHz. Thanks. As I said, I also experienced this issue before, I was just wondering if this might also be related to this high CPU usage and in particular a specific CPU model (which apparently is not the case, as you are on 11th Gen). On 2/28/2025 at 9:01 AM, JorgeB said: In my experience, these errors can be the result of the server being close to exhausting the memory, GUI can become extremely slow, like 1 minute to open the dashboard, try limiting the memory for VMs/docker services, or adding a little more RAM. I was also suspecting this for a while now, but finding this current issue regarding the high CPU usage also seemed to correlate in my case. I just wanted to investigate in this direction. But yeah, I also assume a RAM issue. What I find surprising in my case though: I already limited multiple high RAM users (ZFS, dockers VMs), so my installed 64GB in the dashboard usually report ~80-85% usage. I also already did the `touch /boot/config/fastusr` fix suggested in the changelog. So I probably have to limit (especially ZFS) even more, but we will see. Thanks!
April 28, 20251 yr Chiming in as I am seeing the same consistent log on my htop running Unraid 7.0.1 with various dockers though many unchanged from previous 6.9.X versions. /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50M --log-opt max-file=2 --log-level=fatal --storage-driver=btrfs Running an integrity check seems to also be affected: Build Finished - added 4 files. Duration: 00:02:24. Average speed: 100 B/s Edited April 28, 20251 yr by Waddoo
November 11, 2025Nov 11 Add me to the list of people with this issue. Unraid 7.x (also present in 6.x), 265K (also present on 9700K, Xeon W-2135, but not a dual socket E5-2630L V4, although the latter could potentially be considered "before the issue" chronologically).I'm running 2 Frigate containers as primary server purpose, although issue persists with a single Frigate instance. About once every 30-45 days CPU usage will max out and make the Unraid interface unreachable but leave Frigate accessible (on prior hardware server would entirely hard lock). If I restart Frigate through the Frigate interface I can quickly hop on to Unraid and see the load average in HTOP up to 80... The tricky part is that the issue resolves temporarily if I restart either Frigate container, certainly no clear indication of what the root cause is.I managed to snag this from HTOP at some intermittent point that I could still reach the server.[Main] [I/O] PID USER PRI NI VIRT RES SHR S CPU%▽MEM% TIME+ Command 17890 root 20 0 8121M 190M 0 R 44.6 0.6 0:00.70 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 1525810 root 20 0 8121M 190M 0 S 41.3 0.6 2h10:41 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 17863 root 20 0 8121M 190M 0 R 40.6 0.6 0:00.70 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 18931 root 20 0 8121M 190M 0 S 40.0 0.6 34:43.03 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 3339829 root 20 0 8121M 190M 0 S 39.3 0.6 53:03.99 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 236458 root 20 0 8121M 190M 0 S 37.4 0.6 0:22.28 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 2841797 root 20 0 8121M 190M 0 R 37.4 0.6 1:49.11 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 17889 root 20 0 8121M 190M 0 R 36.7 0.6 0:00.63 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 937490 root 20 0 8121M 190M 0 R 36.7 0.6 0:02.29 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 1303784 root 20 0 8121M 190M 0 R 36.0 0.6 0:40.90 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 1007996 root 20 0 8121M 190M 0 R 35.4 0.6 0:19.77 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 810052 root 20 0 8121M 190M 0 R 33.4 0.6 0:29.51 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 3339841 root 20 0 8121M 190M 0 R 33.4 0.6 19:28.91 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 3438731 root 20 0 8121M 190M 0 S 33.4 0.6 0:01.98 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 1301962 root 20 0 8121M 190M 0 R 32.8 0.6 0:21.12 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 1091186 root 20 0 8121M 190M 0 S 31.5 0.6 0:04.41 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 3438732 root 20 0 8121M 190M 0 R 31.5 0.6 0:01.98 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 1304886 root 20 0 8121M 190M 0 R 30.8 0.6 0:25.29 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 629642 root 20 0 8121M 190M 0 S 30.1 0.6 0:19.65 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 1093325 root 20 0 8121M 190M 0 S 29.5 0.6 0:04.62 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 3748482 root 20 0 8121M 190M 0 S 29.5 0.6 0:09.48 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 1526366 root 20 0 8121M 190M 0 S 28.8 0.6 0:01.46 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 236803 root 20 0 8121M 190M 0 R 27.5 0.6 0:31.44 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 1093315 root 20 0 8121M 190M 0 R 27.5 0.6 0:25.44 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 1304121 root 20 0 8121M 190M 0 S 26.2 0.6 0:43.02 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 17862 root 20 0 8121M 190M 0 S 25.6 0.6 0:00.52 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 17755 root 20 0 8121M 190M 0 S 24.2 0.6 0:00.45 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 432192 root 20 0 8121M 190M 0 R 19.0 0.6 0:31.71 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 16135 root 20 0 8121M 190M 0 R 14.4 0.6 0:00.30 /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --storage-driver=btrfs 2380 root 20 0 83544 8052 4924 S 11.1 0.0 2h18:55 /usr/sbin/winbindd -D 119608 root 20 0 1242M 30536 0 S 8.5 0.1 1h33:27 containerd --config /var/run/docker/containerd/containerd.toml --log-level fatal 17464 root 20 0 1496M 25624 0 S 6.6 0.1 0:02.16 libvirtd -d -l -f /etc/libvirt/libvirtd.conf -p /var/run/libvirt/libvirtd.pid 13320 root 20 0 21.3G 182M 57884 S 4.6 0.6 4h09:54 node /usr/local/unraid-api/dist/main.js 17298 root 20 0 1496M 25624 4676 S 3.3 0.1 0:39.41 libvirtd -d -l -f /etc/libvirt/libvirtd.conf -p /var/run/libvirt/libvirtd.pid 19113 root 20 0 7336M 2178M 9728 S 3.3 6.9 2d02h48m /usr/bin/qemu-system-x86_64 -name guest=HomeAssistant,debug-threads=on -S -object {"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-1-HomeAssistant/master-key.aes"} -blockdev {"driver":"file","filename":"/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"} -blockdev {"node-name":"libvirt-pflash0 2382 root 20 0 83392 8972 5120 S 2.6 0.0 24:08.12 /usr/sbin/winbindd -D 3444529 root 20 0 13500 5552 4112 S 2.6 0.0 3:14.21 /usr/bin/ttyd -d0 -W -t rendererType canvas -t closeOnDisconnect true -t disableLeaveAlert true -t theme {'background':'black'} -t fontSize 15 -t fontFamily monospace -s9 -om1 -i /var/run/syslog.sock /usr/local/emhttp/webGui/scripts/run_cmd tail -f -n 90 /var/log/syslog 2359 root 20 0 88356 9496 6312 S 2.0 0.0 4:51.07 /usr/sbin/smbd -D 1173742 root 20 0 12280 9760 3200 R 2.0 0.0 0:28.25 htop 3357549 root 20 0 13500 5856 4416 S 2.0 0.0 11:30.54 /usr/bin/ttyd -d0 -W -t rendererType canvas -t closeOnDisconnect true -t disableLeaveAlert true -t theme {'background':'black'} -t fontSize 15 -t fontFamily monospace -s9 -om1 -i /var/tmp/Frigate-Test.log.sock /usr/local/emhttp/webGui/scripts/run_cmd docker logs -f -n 90 Frigate-Test 3633332 root 20 0 6196 4768 2924 S 2.0 0.0 28:06.30 /bin/bash /usr/local/emhttp/plugins/ca.mover.tuning/age_mover start 19217 root 20 0 7336M 2178M 0 R 1.3 6.9 8h11:23 /usr/bin/qemu-system-x86_64 -name guest=HomeAssistant,debug-threads=on -S -object {"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-1-HomeAssistant/master-key.aes"} -blockdev {"driver":"file","filename":"/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"} -blockdev {"node-name":"libvirt-pflash0
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.