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.

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

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

Okay, since posting I did the following: - stopped docker service and ran the mover - DNS was set to automatic and being handled by my pihole. I whitelisted Unraid completely within pihole and also set DNS to static and chose OpenDNS and Google for DNS servers Everything is working normally and the error is gone. I'm not absolutely clear on what ended up doing it--I think it may have just been DNS the whole time, but I'm fairly paranoid by default and not completely trusting I've solved the error. I guess time will tell.

Hi everyone, I know this topic has come up in the past, but all the previous threads I've found don't seem to end with the issue being resolved. Here is the full error message: I have Plex pointed to /dev/shm for transcoding. No other container, as far as I'm aware, is pointed to /tmp. This error seems to happen consistently about once a month and the result is I can no longer update apps or access the CA apps browser. The only resolution is to reboot, so that further confirms there's something writing to and filling up /tmp but I can't figure out what it is. Can someone point me to how I can begin to narrow down what may be doing this? Thanks! 😃