February 24, 20251 yr Community Expert Quote docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: unable to apply cgroup configuration: mkdir /sys/fs/cgroup/docker/fbeabbda1c363dfdf437ba38ca052d9a151176e3e55c5904e9f65a7f1a30bc36: no space left on device: unknown. The command failed. I'm running unRAID 6.12.14 Can someone help me narrow this issue down preventing installation of new dockers? I check my array, cache pools, and USB boot device; there is plenty of space on all.
February 24, 20251 yr Author Community Expert I found this from the Fix Common Problems plugin: Quote /var/log is getting full (currently 100 % used) syslog could be potentially being spammed with error messages. A reboot of your server will at least temporarily solve this problem I will check my syslog as I am trying to avoid a reboot. I see no syslog messages loading: Can I increase the size of /var/log or adjust retention...? Edited February 24, 20251 yr by gurulee
February 24, 20251 yr Author Community Expert On 2/24/2025 at 10:02 AM, trurl said: Attach Diagnostics to your NEXT post in this thread. @trurl thank you for the quick reply and guidance. I am attaching my diagnostic here for review. 🙂 🙏 Edited February 25, 20251 yr by gurulee removed diag file post resolution
February 24, 20251 yr Community Expert Solution Your log is filling up with these many times per second. Feb 12 05:26:09 Tower sshd-session[11597]: Starting session: command for root from 192.168.100.143 port 55868 id 1 Feb 12 05:26:09 Tower sshd-session[11597]: Close session: user root from 192.168.100.143 port 55868 id 0 See if you can figure out how to stop that.
February 24, 20251 yr Community Expert After I filter all that out, there is nothing left to see. Make it quit, reboot, and post new diagnostics.
February 24, 20251 yr Author Community Expert 7 minutes ago, trurl said: Your log is filling up with these many times per second. Feb 12 05:26:09 Tower sshd-session[11597]: Starting session: command for root from 192.168.100.143 port 55868 id 1 Feb 12 05:26:09 Tower sshd-session[11597]: Close session: user root from 192.168.100.143 port 55868 id 0 See if you can figure out how to stop that. That is my Home-Assistant system using the below integration to monitor my unRAID server: https://github.com/domalab/ha-unraid/wiki It configured on the Home-Assistant side like this:
February 24, 20251 yr Community Expert 54 minutes ago, trurl said: Make it quit, reboot, and post new diagnostics.
February 24, 20251 yr Author Community Expert This was the resolution for these repeated and expected ssh log messages from the home-assistant integration: https://github.com/domalab/ha-unraid/wiki/Troubleshooting#ssh-session-log-spam Edited February 24, 20251 yr by gurulee
February 25, 20251 yr Community Expert Do you mean you have fixed your syslog problem? What about your docker problem?
February 25, 20251 yr Author Community Expert 10 hours ago, trurl said: Do you mean you have fixed your syslog problem? What about your docker problem? Docker problem preventing new docker installs was related to no space left in log path. Suppressing the log spamming from the home-assistant integration with the above noted script will prevent reoccurrence.
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.