Hi All,

 

I hoping for a bit of help as despite a few days of googling and tinkering I'm no closer with solving my issue (so apologies of it's stupidly simple!).  Everything has been working fine for ages until a few days ago when my cache drive died - which had my appdata and system shares on, not backed up of course. I've put a new drive in and the server is up and running but I'm having trouble getting my docker containers reinstalled.

 

At first, I thought it was an issue with losing my appdata share but now I think it's a network issue with docker. All my network connections seem to work fine (i.e. I can access all my shares from the network, use the GUI , search the Apps tab etc) except when it comes to Docker.

 

Here's a list of things I've found/tried during my tinkering;

 

• Switching it off and on again (the server and docker) - seems to work most times I have any issues but not this time!
• Using a few different docker images, from an old back up to a brand new one (i.e. delete and let docker recreate) - no difference.
• All my docker templates are saved and can be selected when adding a container - it fails when it tries to download (see attached screenshot for the error).
• Changing the network settings in the docker settings didn't seem to make any difference.
• I get this error when trying to reinstall any of my previous containers (either through the docker tab or via CA) or install a brand new docker container but not when downloading plugins from CA (yes, I'll be backing up my Appdata share now...).

 

I've attached the usual diagnostics info - as far as I can tell these are the same settings that worked before the cache drive died and I'm getting the above behaviour with now.

 

Any help would be appreciate - the SO is getting restless without Emby...

 

Cheers

mooserver-diagnostics-20230612-2257.zip

I should also add that 192.168.0.1 is the IP of my router (that also does DHCP duties) and 192.168.0.12 is the IP of Mooserver

Just in terms of an update, I managed to solve the original issue described above, it was a DNS issue which just needed me to change the default DNS on my router from the PiHole docker (that wasn't there) to something else whilst the dockers re-downloaded. Now I'm on to the next bunch of problems as Unraid and Docker are still not happy - after 3 days of working, the docker service is now refusing to start after restarting the server. I'll do some digging and post a new thread if it the answer alludes me...