helpermonkey

will do. thanks

For the past few days, my server starts producing Exit Status Errors. Unraid seems to stop working at this juncture, so while i can still ping my server on my local network, everything else goes kaput. I have a KVM hooked up to the server and when looking at it - i see a bunch of Exit Status Errors and when i'm prompted to login - it kicks back with an error: /usr/share/bash-completion/bash_completion: Input/output error. Any ideas? buddha-diagnostics-20240523-1152.zip

I have a slew of entries in this field in my config (i don't remember why - as i set this up years ago). Is it safe to delete all of those and just go with 1.0.0.1 and 8.8.8.8? I am happy to post all the addresses i have in that key field if that would help.

where do you change the DNS servers for this?

thanks!

thanks for that tip. A question about the instructions for rebuild-dndc.... https://github.com/elmerfdz/rebuild-dndc on step 2 where it talks about ... docker network create container:master_container_name do i need to change master_container_name to binhex-delugevpn?

just deleting them is sufficient.

still having this problem - is there a paid support service available? this is quite problematic.

just thought i'd throw this back up to the top.

Just a bump to see how to get this fixed.

Whenever an update for one of my docker images becomes available, my unraid installtion ends up with orphan images which in turn creates high image disk utilization. The only solution I've found is to log in every few days and delete the orphan images manually. Attached are my diagnostics, as well as a notification list and my docker page. i deleted those orphan images and applied the updates after collecting the diagnostics that are attached. Is it possible this is a bug? I have mentioned this problem here in the past but we have not been able to uncover a solution. Any suggestions appreciated. buddha-diagnostics-20210825-1229.zip

rather than start a new thread - i thought i'd add to this one. For those that see this post here's a short summary of my situation: Whenever my server finds an update of an installed docker, i end up with an orphaned docker image. These dockers are no automatically updating. I have suggested it might be a bug but mindful that I am not technically capable of determining that. Any suggestions on things to try would be appreciated.

@Squidwould you happen to have any thoughts?

roger! thanks for all your help to this point.

@trurl would you have any thoughts on this? was hoping some others might help take the weight of your shoulders. I left the server alone for a few days - came back today and there were 7 orphans with 5 images needing updates applied. I'm curious that the Total Data Pulled is always 0 B for any docker.... is this unrelated to the size of the file or is it because the data is downloaded ahead of time and then the update is applied so the dockder run doesn't show the download? (or something else? again out of my depth here).