Error response from daemon: OCI runtime create failed

[ChaOConnor]

Good Evening,

 

My unRaid server was running slow and I'm getting ready to swap some smaller disks for larger ones.  I rebooted and after reboot, Docker failed to start.  I couldn't find anything that was a smoking gun, so some diagnosis steps suggested to delete the docker.img and recreate.  I can't create any new dockers, they always fail at the Error response from daemon: OCI runtime create failed.

 

I've attached my log files, not sure what is going on.  Has anyone seen this before?  Searching the forum it recommends removing a line from the "go" file, but I don't have that line (related to a Binhex container).

 

Appreciate any help anyone can offer!

 

 

rebeldata-syslog-20211106-0107.zip

[ChaOConnor]

Additional info, the cache drive is not full either.  That seems to come up a lot.  I've deleted the docker.img file multiple times, rebooted multiple times, those aren't resolving it.

[Squid]

You need to post your diagnostics

[ChaOConnor]

I'm so sorry, I'm an idiot and thought that was what I had attached.  Thank you!

rebeldata-diagnostics-20211106-1146.zip

Edited November 6, 2021 by ChaOConnor

[Squid]

Are you sure that you're not applying that binhex patch via a user script?

[ChaOConnor]

I can't see any user scripts that are applying anything or run automatically except the change login screen script.  Are you seeing something that makes you think it's being run somewhere?  Thank you!

[ChaOConnor]

Okay, nothing was working.  I ended up backing up the USB drive and re-ran the USB creator.  Restored my configs and now it's working.  I'm really at a loss here though.  I hadn't been on the server for a month, no changes I mean.  It was just happily sharing out media to Plex and them bam, one reboot and it was all toast.  Very odd.  I'll add dockers back one at a time to see if anything triggers it again.