Docker Execution Errors - "Failed to Start Shim...no space left on device"

[lunchbox]

Hi everyone,

 

Today some of my containers stopped and could not be restarted. Trying to start these containers results in an "Execution Error" pop-up. When I actually get the docker run command to run I get an error message that I've attached as a screenshot.

 

 

My docker image doesn't seem to be out of space, neither does cache or system so I'm stumped as to what is causing this issue? All my paths seem to be in order and no ports seem to conflict.

 

 

 

I just tried restarting docker completely and now get the following error:

 

 

Can anyone offer me some guidance here?

 

 

lunchbox-diagnostics-20230509-0003.zip

Edited May 9, 2023 by lunchbox
added some more info and updated diagnostics

[JorgeB]

Reboot and post new diags after array start.

[lunchbox]

Hey, thanks for the reply. Here are my new diags after reboot.

 

I went ahead last night perhaps prematurely and deleted and rebuilt my docker image and reinstalled all containers. Things are working and containers can be stopped and started, but I'm wary this has not actually fixed the issues and that they'll return again in time. Although even though containers were working again I am now having trouble with sonarr being able to see and import downloaded items. Could be related or completely unrelated.

 

Thanks again for taking a look.

lunchbox-diagnostics-20230509-1241.zip

[JorgeB]

Log looks normal and if everything is working just post new diags if issues come back.

[lunchbox]

Alright, thanks so much!

 

Now onto my sonarr issue, which seems to be unrelated. I should be able to find that on my own.