SliMat Posted July 21, 2020 Share Posted July 21, 2020 Hi When I go into my DOCKER tab all my dockers are listed as VERSION "not available"; Does anyone else have this, or know how to fix it? The only work around I have found is to switch to advanced view and run "force update"... this then shows that the latest version is installed. But soon after, if I go back into DOCKERs it shows "not available" again. I have two HP servers and this persistent annoyance only happens on one! Any pointers? Thanks 2 Quote Link to comment
SliMat Posted July 27, 2020 Author Share Posted July 27, 2020 Update - I forced an update just after posting this, so they all said "up-to-date", then today when I checked again, they all say "not available" again 😞 Quote Link to comment
casperse Posted August 9, 2020 Share Posted August 9, 2020 I am also getting something like this one is fine the other is "Not available" I have updated and rebooted the server what's next? Quote Link to comment
tuxbass Posted August 27, 2020 Share Posted August 27, 2020 Same here - just one of the containers is reporting not avail. Quote Link to comment
Jahf Posted October 6, 2020 Share Posted October 6, 2020 Seeing this here as well today. Seems to be something I can live with so I'm just documenting what is going on. Started with my binhex-deluge docker reporting "not available", all others showed updated (I did an update all a few days ago). Updated my linuxserver/letsencrypt to be linuxserver/swag. Restarted my server to fix a Web UI glitch where one of my CPU cores was showing 100% even though htop showed very low usage. After the restart I started up my Dockers and ... now ALL except linuxserver/swag are showing "not available" (swag was the only one I had manually updated today). Clicked "check for updates" and "unavailable" is gone (as in I see either "up-to-date" or "update-ready" for all Dockers) I use pihole and it's the next-to-last Docker to start in a "start all" sequence. And sure enough as soon as it was active the last in my sequence (swag) showed status. So I have to wonder if folks are seeing this issue due to one of their dockers being needed to be running for the update check to run. 1 Quote Link to comment
Squid Posted October 6, 2020 Share Posted October 6, 2020 Is Unraid running through piHole? If so, then best to not have it do so as that introduces a whole other layer of complexity, and there's no real reason to run it's internet through it in the first place. 1 3 Quote Link to comment
yayitazale Posted October 20, 2020 Share Posted October 20, 2020 (edited) same problem here I just force the update of the first docker on the list and then hitted check for updates and now all the containesr are up-to-date again... Edited October 20, 2020 by yayitazale Quote Link to comment
SliMat Posted December 10, 2020 Author Share Posted December 10, 2020 I thought I would bump this as its been several months and I am still having this problem. I upgraded my licence to Pro a few nights ago and replaced my server with a newer DL380 with 18 HDDs - everything works, but just frustrating that this machine lists all the dockers as "Version not available" while my HP Microserver works fine? I have read a few more cases of this problem with other users - so can anyone offer any thoughts on how to fix it? At the moment I have to force an update on all the dockers for it to show "up to date" but a short while later they all say "not available" again 😞 Quote Link to comment
CoZ Posted December 10, 2020 Share Posted December 10, 2020 On 10/5/2020 at 11:51 PM, Squid said: Is Unraid running through piHole? If so, then best to not have it do so as that introduces a whole other layer of complexity, and there's no real reason to run it's internet through it in the first place. How does one stop it from running through piHole? If the piHole docker is on the server and the DNS settings on the WAN part of the router point to the piHole's docker IP address, how can you stop unRaid from running through it? Quote Link to comment
chancedonmillion Posted February 13, 2021 Share Posted February 13, 2021 I was running into the same issue. Docker Version "not available" In my case Fix Common Problems plugin was reporting "Unable to communicate with GitHub.com". This issue surfaced after setting unbound Pi-hole as the DNS on my home network. My workaround was as follows. 1. disable VM and docker in unraid settings 2. change the DNS in unraid IP settings to 1.1.1.1 (use whatever DNS you'd like) rather than my home router IP / Pi-hole 3. re-enable VMs and docker in unraid settings 4. toggle advanced view and force update containers in the docker tab of unraid After the following the above steps all contains show as up to date and are auto updating again. 6 2 Quote Link to comment
Cold Ass Honkey Posted February 20, 2021 Share Posted February 20, 2021 Thank you, chancedonmillion. This was plaguing a couple of docker containers on my server too (non Pi-hole.) Not only did your workaround fix the "not available" issue, but greatly increased the speed and responsiveness of my Unraid server in general! I previously had the DNS settings directly pointing to my router exclusively. 1 1 Quote Link to comment
Todo88 Posted March 19, 2021 Share Posted March 19, 2021 I was stuck with "not available" on all of my Docker images and changing my server DNS from Pi-Hole to Cloudflare worked great, thanks! Quote Link to comment
bonienl Posted March 19, 2021 Share Posted March 19, 2021 A general tip for those people you use pi-hole as local DNS server. Always make sure your Unraid server does NOT use the pi-hole DNS server, but a "regular" DNS server instead, e.g. google or cloudflare. If you want a docker container to use the pi-hole server, you can add the option --dns=<pi-hole ip-address> in the extra parameters field of the container. 1 Quote Link to comment
Zonediver Posted March 20, 2021 Share Posted March 20, 2021 On 12/10/2020 at 6:06 PM, CoZ said: How does one stop it from running through piHole? unraid has its own DNS-Settings Quote Link to comment
vanrhyn Posted April 3, 2021 Share Posted April 3, 2021 On 2/13/2021 at 12:54 PM, chancedonmillion said: I was running into the same issue. Docker Version "not available" In my case Fix Common Problems plugin was reporting "Unable to communicate with GitHub.com". This issue surfaced after setting unbound Pi-hole as the DNS on my home network. My workaround was as follows. 1. disable VM and docker in unraid settings 2. change the DNS in unraid IP settings to 1.1.1.1 (use whatever DNS you'd like) rather than my home router IP / Pi-hole 3. re-enable VMs and docker in unraid settings 4. toggle advanced view and force update containers in the docker tab of unraid After the following the above steps all contains show as up to date and are auto updating again. How do I change the DNS in UNraid IP Quote Link to comment
Squid Posted April 3, 2021 Share Posted April 3, 2021 Settings - Network Settings Quote Link to comment
vw-kombi Posted April 4, 2021 Share Posted April 4, 2021 This started happening to me as of today. My DNS however is set to cloudflares 'newer' 1.1.1.2 and 1.0.0.2 DNS servers. The ones with malware protection are 1.1.1.2. Maybe whatever unraid is using has got onto that list of nasties ? Quote Link to comment
bastl Posted April 4, 2021 Share Posted April 4, 2021 Same here for me, started yesterday. Yesterday i clicked on "check for updates" and mariadb and collabora came up with an update. Only collabora showed not available. After updating mariadb I thought, ok, your internet has stability issues anyways, check again tomorrow. And today it shows the following. Not all are unavailable and Collabora shows a update now. Weird! I've checked pihole if anything came up in the query log, but nothing is blocked. I updated all packages on pihole (on a pi4), updated unbounds local root config, restarted the pi and rechecked for updates. Now only netdata and collabora showed an update, no unavailable ones. Updating netdata wen't fine, recheck for updates and only collabora left with an update. Looks like it works again for me. Quote Link to comment
Amigaz Posted April 4, 2021 Share Posted April 4, 2021 Same problem here ... or when doing "check for updates" on the docker section it checks for updates forever. Quote Link to comment
rb47 Posted April 11, 2021 Share Posted April 11, 2021 I too experienced this for the first time a few days ago on Unraid 6.9.1. All of my containers read "not available" for their respective versions. I am not using Pi-hole and fiddling with DNS and stopping/starting the Docker service did not fix the issue so I left it be. Today, I tried to manually "Check for Updates" under the Docker tab and, after an uncomfortably long wait, all of the correct version numbers were back. I was able then to successfully update all containers. Quote Link to comment
bluuurb Posted May 14, 2021 Share Posted May 14, 2021 Noticed this issue today as well. Updates are still being done via the CA Auto update plugin but no way to check the versions now. Quote Link to comment
Squid Posted May 14, 2021 Share Posted May 14, 2021 44 minutes ago, bluuurb said: Noticed this issue today as well. Updates are still being done via the CA Auto update plugin but no way to check the versions now. 2 5 Quote Link to comment
daemon_of_chaos Posted May 14, 2021 Share Posted May 14, 2021 What is the fix when encountering this problem and pihole is not present in the network? Quote Link to comment
Recommended Posts
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.