MrAndyBurns

Great work @HyperV and @ich777 and @ephdisk ... I still needed this fix as I am still having VM problems moving to 6.9.x (Xpenology - kernel is too new) ... but all 24 dockers now showing status correctly

Thank you HyperV for the fix .. I had the same issue where all were 'not available' after a simple restart ... changed DNS/forced updates etc but no win .... this worked a treat If it help anybody else, in nano (editor) you can goto line 457 to add the magic 'i' above by typing adding the line to the command ... for example in a terminal window type nano +457 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php Thanks once again HyperV

Probably just FYI ... I have been running Xpenology as a VM on my Unraid for about a year. Xpenology was my main NAS on a few bare metal builds but I liked the looks of Unriad and have been very happy on 6.8.3 (mainly spinning down drives and SSD cache pool for VM's dockers). I have setup Xpenology with a virtual disk, changed the virtio network adapter to e1000e as per many of the forums and works well. HOWEVER I have recently upgraded to 6.9.1 and found that I can not get Xpenology to run and it appears to panic so does not even get a network address (just like the old days). I have to say I didn't spend too long trying to fix and ended up rolling back to 6.8.3 (no data loss, just needed to use the backup of my flash disk to get the cache pool back). If anybody has been playing and worked a way around this or spotted whats causing the problem please post.