i am getting this error:

"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/1c0b39233374276b0b6f2e860f93dcfa1660d5588da8a672688d21c4af1ec2f1: no space left on device: unknown"

 

i have tried deleting the log files in /run and that along with restarting the docker service worked once. now no matter what i do  i cant update or start any new containers

tower-diagnostics-20240514-1701.zip

Try recreating the docker image:

 

https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file

Also see below if you have any custom docker networks:

https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks

i have tried this and clearing the log files but nothing fixes it. a temp solution is to reboot but eventually i end up with the same error

Syslog you posted has a lot of spam, do you remember the time code it last happened? Or post new diags just after it happens again.

it just happened at 1:56 am pst. heres my new diagnostic

tower-diagnostics-20240602-0157.zip

There's constant SSH spam which I assume you know what is causing it?

 

But these are also constant and not normal:

Jun  2 01:57:26 Tower elogind-daemon[1888]: Failed to create cgroup c88335: No space left on device
Jun  2 01:57:26 Tower sshd[21090]: pam_elogind(sshd:session): Failed to create session: No space left on device

 

the ssh is a fan script

4 minutes ago, JorgeB said:

But these are also constant and not normal:

Jun  2 01:57:26 Tower elogind-daemon[1888]: Failed to create cgroup c88335: No space left on device
Jun  2 01:57:26 Tower sshd[21090]: pam_elogind(sshd:session): Failed to create session: No space left on device

 

this is the issue and i cant figure out what is causing it

Try booting in safe mode, and also stop all scripts, you have have then running outside user scripts.

i reverted back to 6.12.9  i didn't start having this issue till i upgraded to 6.12.10. i will report back in a day or so to see if it continues

Edited June 2, 20242 yr by lordbeavis

so far so good. i will update in a couple more days

im still having this issue and have to reboot my server at least once a week

this seems to be related to my issue

 

 

https://github.com/moby/moby/issues/29638

i think i may have found out my issue, it seems that one of my cache pools may have been corrupted or a drive damaged. i have removed one set of drives from my server and removed the other 2 pools from my shares. after copying the files back to the array i havent had the issue yet in 3 days