After updating from 6.9.2 to 6.11.5 my docker and plugins installs and commands have broken. 

for plugins when i try and install a plugin via the app center i get an error like below

 

plugin: installing: dynamix.file.manager.plg
Executing hook script: pre_plugin_checks
plugin: downloading: dynamix.file.manager.plg ...
plugin: dynamix.file.manager.plg download failure: Network failure
Executing hook script: post_plugin_checks

 

This occurs on any plugin i try.

The bigger issue though is my docker. existing containers run but seem abit buggy now (could be unrelated to the main issue though) however i cannot install any new docker containers or apps and when i run docker commands in unraid terminal i get errors and it is not responding.

The error is always the same
 

error: Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io on 8.8.4.4:53: write udp 192.168.1.131:33262->8.8.4.4:53: write: operation not permitted

I have tried the following solutions.
 

• Restarting unraid
• Restarting docker by stopping docker using the unraid UI to turn it off and then turn it back on
• updated my /etc/resolv.conf dns values from 8.8.8.8 and 1.0.0.1 to 8.8.8.8 and 8.8.4.4 (based on a previous post from someone with similar error)
• most posts about this i find online seem to tackle this as a dns issue but the error to me indicates "write permissions" and my unraid network is working and i can even oddly updating existing running containers so this feels like my docker install on unraid is broken/misconfigured since the update
• under the tools i tried "Docker Safe New Perms" and the "new permissions" thinking "write permissions" might be by updating the permissions

 

I would rather not restore to the old unraid version as it may not fix the issue anyway and i upgraded because it stated support was/has ended for that version.

 

I am a novice at unraid and linux so if i need to provide diagnostics or other steps let me know the steps to do it.

thanks in advance for your help

Edited November 30, 20223 yr by Barry Wright

Post your diagnostics

I seem to have fixed the issue (for now at least). After all of the above steps i just tried another restart of the entire server and this time it worked. im guessing one of the above steps fixed the issue but required a reboot to apply changes properly.
Will leave this for anyone else who hits this issue