Last week I was tinkering with the location of VM's and moved system shares on and off the cache.  Immediately afterwards, I noticed I'd broken the VM's and all 3 dockers ( Krusader, Duplicati and Shinobi).  Updating the container paths fixed the VM's and the Krusader docker, but Duplicati and Shinobi's WebUis were unresponsive (the services start ok).

 

Got side tracked with work, even updated to 6.8 in there too, but today back to trying to fix the remaining 2 dockers.

 

I mucked about, uninstalled the dockers, deleted their old configs, and reinstalled, with no luck.  Came back later, Shinobi's WebUI started working, and I'm not sure I actually didn't anything.  Duplicati's UI is still broken though. 

 

Duplicati's console seems to work, and from unRAID's terminal, I can ping the docker's IP.  I get connection refused when I try wget http://172.17.0.3:8200

 

Any ideas where to start looking?

 

Looks like moving VMs and Docker config data around might have been coincidental. 

 

Dockers are still running, but sooner or later their WebUI stops responding, sometimes while I'm using it.  No doubt related, I'm also getting 'no connection to github.com' errors.  In fact, I’ve now noticed that even pinging hosts out on the internet from the unRAID command line, the connection seems to drop in and out (flaps between getting replies, and host unreachable)

 

VM’s all connect to the internet fine during this, so my temp workaround for the Dockers is assigning Dockers a custom network connection with an IP on same subnet as the unRAID box and the rest of the network.  But the underlying problem is still there, as evidenced by intermittent connection to the internet/

 

I'd really appreciate even a clue as to where to start looking.  Logs are there taken from a few seconds ago, while the fault is happening.

pornstar-diagnostics-20191226-1404.zip