January 29Jan 29 Hi all,My cache drive failed and I replaced it and used Appdata backup to recover my dockers.After re-installing them all, they appear to be working but I can't access any of them. It just says "Unable to connect".Not really sure how to fix this.Any advice would be appreciated.Cheers. tower-diagnostics-20260130-0751.zip
January 29Jan 29 Community Expert Probably not the reason for your problem, but your system share has files on the array. Probably you had Docker and/or VM Manager enabled when cache was missing.
January 29Jan 29 Community Expert 2 minutes ago, trurl said:Probably not the reason for your problemandJan 30 07:51:03 Tower root: Fix Common Problems: Warning: Share etc is an implied array-only share, but files / folders exist on the cache
January 29Jan 29 Community Expert There are 3 parts to recreating dockers explained here:https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/Is that what you did? Including that last part about custom docker networks?
January 29Jan 29 Author 37 minutes ago, trurl said:There are 3 parts to recreating dockers explained here:https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/Is that what you did? Including that last part about custom docker networks?By order.I didn't have a corrupted image. The SSD was dead. I put in a new SSD. A new file system was created and I restored a back up of Appdata using the Appdata backup tool.I restored the previous dockers using the reinstall function in the app area. It has used my old settings.At first, I forgot to create the custom networks and the dockers didn't work. I quickly realised and did recreate the custom docker network. I restarted the dockers but still don't have access. Edited January 29Jan 29 by bobalot more information
January 29Jan 29 Author 41 minutes ago, trurl said:Why are you using a docker folder instead of a docker.img?I switched over to the folder structure a while back (before my SSD failure). Forgot the reason.I think it was to be able to access the files and I kept getting issues with teaching the maximum docker size. Edited January 29Jan 29 by bobalot
January 29Jan 29 Community Expert The usual cause of growing docker.img usage is an application writing to a path that isn't mapped.What is in the system folder on disk3?
January 29Jan 29 Community Expert 3 minutes ago, trurl said:What is in the system folder on disk3?And what is in the system folder on cache?
January 29Jan 29 Author 23 minutes ago, trurl said:The usual cause of growing docker.img usage is an application writing to a path that isn't mapped.What is in the system folder on disk3?Just a folder called libvertThere is a large img file. Edited January 29Jan 29 by bobalot More information
January 29Jan 29 Author 21 minutes ago, trurl said:And what is in the system folder on cache?libvert is empty
January 29Jan 29 Community Expert 8 minutes ago, bobalot said:There is a large img file.That is the default size for libvirt.imgBut it belongs on cache.You will have to disable VM Manager before you can move it.Of course, none of that has anything to do with your dockers, but still good to clean that up.
January 29Jan 29 Community Expert How are you trying to go to the webUI of that container in the first post?Are you clicking on its icon and selecting WebUI?Is that from a monitor attached to the server, or from another computer on the network?
January 29Jan 29 Author 1 minute ago, trurl said:How are you trying to go to the webUI of that container in the first post?Are you clicking on its icon and selecting WebUI?Is that from a monitor attached to the server, or from another computer on the network?I just type in my IP on the network and the port.It's from another computer on the network.I just noticed that I can access my unmanic docker (which isn't on a custom network - not sure if that is relevant).
January 29Jan 29 Community Expert 24 minutes ago, trurl said:clicking on its icon and selecting WebUIWhat happens like that?
January 29Jan 29 Author 17 minutes ago, trurl said:What happens like that?That hasn't worked in Foldierview2 for a while (before the SSD failure, plugin needs the dev to update this bug) but I did try that in the apps menu for the dockers that were installed (selecting the docker and clicking webui) and it didn't work.Been checking some other dockers, this issue seems to be limited to anything on the custom docker.
January 29Jan 29 Author 56 minutes ago, trurl said:That is the default size for libvirt.imgBut it belongs on cache.You will have to disable VM Manager before you can move it.Of course, none of that has anything to do with your dockers, but still good to clean that up.Weird. I thought I have VMs turned off.Thanks. I have turned it off.
January 29Jan 29 Community Expert 3 minutes ago, bobalot said:That hasn't worked in Foldierview2What happens if you remove that plugin? Can you click on the icon and select WebUI then?
January 30Jan 30 Author Solution 50 minutes ago, trurl said:What happens if you remove that plugin? Can you click on the icon and select WebUI then?I managed to fix some of them by changing the WebUI from http://[IP]:[PORT] to the hard coded address (192.168.1.4:XXXX).It must have been that plugin. Had to go to work. When I get back from work, I'll remove it all together and see what happens.Most of the dockers are accessible now. A few not working.Not really sure why that plugin is causing and issue if it didn't before my old SSD failed. Edited January 30Jan 30 by bobalot
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.