May 3, 20251 yr Hi all, can someone help me out please? This happened during the monthly parity check. I was previously on v6.12.14 and then updated to v7.0.1 hoping it'll automagically solve it after a reboot. No dice. I've attached the diagnostic zip. I'm also away and don't have physical access. I've set up a wireguard tunnel for remote access. Thank you in advance, tower-diagnostics-20250503-1837.zip Edited May 3, 20251 yr by vurt
May 3, 20251 yr Community Expert Solution Docker image is corrupt, delete and recreate: https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file Then: https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications Also see below if you have any custom docker networks: https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks
May 3, 20251 yr Author 9 minutes ago, JorgeB said: Docker image is corrupt, delete and recreate: Also see below if you have any custom docker networks: https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks Thank you! I think I might have a custom network, i was following a guide. From what I read in your link, custom networks are gone with the deleted docker image. When I'm re-adding the containers, does the template remember the Network Type from previously? Because right now, eg, radarr's network type is None, but when I click on the dropdown, I see an option for Custom: br0. And to complicate matters, I thought I'd created a custom network called "lsio" because I was following a guide for Linux Server's containers. I hope that didn't sound as confusing as I feel.
May 3, 20251 yr Community Expert 6 minutes ago, vurt said: does the template remember the Network Type from previously? I believe so, as long as it exists with the same name, and you should be able to see the name of the network a container was using by opening its template (config\plugins\dockerMan\templates-user on the flash drive)
May 3, 20251 yr Author 3 hours ago, JorgeB said: I believe so, as long as it exists with the same name, and you should be able to see the name of the network a container was using by opening its template (config\plugins\dockerMan\templates-user on the flash drive) I did as you suggested and indeed found "lsio" in some of the files. The odd thing is, after I recreated the docker img, Custom:br0 is already there but Custom:lsio wasn't. Anyway I did "docker network create lsio" and recreated the custom network. I've since managed to bring back a few of the containers. This is a different problem now. Sonarr won't start and at the end of the container install log, shows this error: docker: Error response from daemon: error while creating mount source path '/mnt/user/appdata/downloads': mkdir /mnt/user: file exists. Audiobookshelf also shows a similar error: docker: Error response from daemon: error while creating mount source path '/mnt/user/appdata/downloads': mkdir /mnt/user: file exists. Radarr shows this error: unable to open database file I think the Radarr error might be solved if I can find restore a backup of the database. But I'm sure what's going on with Sonarr and Audiobookshelf—would you have any ideas? thank you for your help!
May 4, 20251 yr Community Expert Cannot really help with specific container issues, look for their support thread:
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.