right-hand-cannibal6081

Hello, I updated my Unraid instance from 6.12.4 to 6.12.6 today. I disabled auto-start for all of my docker containers prior to updating as I wanted to run a large amount of container updates afterwards, however I'm having significant difficulty getting things back up now. When I attempt to start 1 container, it shows started after loading for a few seconds. If I reload the page however, it shows stopped again. Attempting to start it again, or start any of my other containers results in a generic "Server Error" pop-up from unraid. If I attempt to update any of my containers Docker will pull images fine, but fail to remove the container with a "Error: Server error"; because this fails to remove the container, it will also fail the follow-up docker run/create command with a conflict error since the container name already exists: Error response from daemon: Conflict. The container name "/sonarr" is already in use by container "7e95a641c5ae73a55e2407fecd1b47da6e7dd198fd9f212666c58647007ae329". You have to remove (or rename) that container to be able to reuse that name. I tried disabling docker in settings to shutdown the daemon, then enabled it again with the same issues. I also ran a scrub and expanded the disk img for docker to no help either. I have attached two diagnostic reports, one is from the boot after the update and the other is after restarting unraid to see if that would resolve the issue. I also just got a warning from fix common issues: Unable to write to Docker Image Docker Image either full or corrupted. This is after I did the aforementioned scrub and expansion of the image without error. Do I need to delete my docker img, and if so, would that have any repercussions on data, configs, etc. for containers? chatham-diagnostics-20240111-1235.zip chatham-diagnostics-20240111-1226.zip