mayberts Posted July 31, 2023 Share Posted July 31, 2023 I'm also getting this issue on 6.12.3, but I don't have any custom networks Quote Link to comment
svartpest Posted September 24, 2023 Share Posted September 24, 2023 I also have this problem on 6.12.4 and it seems to affect random containers. I don't see any difference based on what network the container uses or actual update availability. Search has turned up very few mentions of this problem since 6.12.0 became available. Only solution I've found personally is to delete each affected container when this happens and reinstall. Has anyone found a better solution? Quote Link to comment
bombz Posted January 2 Share Posted January 2 Saw this concern random docker containers are showing 'not available' when attempting to update today....after updating to the latest CA Currently running v6.12.4 Is there a workaround for this concern, or perhaps has been patched in the latest OS 6.12.6? Quote Link to comment
Tarnous Posted January 5 Share Posted January 5 (edited) Hi ! same here, thursday v 6.12.6 tried force update same problem Edited January 5 by Tarnous Quote Link to comment
cynikaly Posted January 5 Share Posted January 5 Hello, same problem. Appeared after the recent 6.12.6 update again. Quote Link to comment
eraser1320 Posted January 8 Share Posted January 8 On 1/5/2024 at 4:54 PM, cynikaly said: Hello, same problem. Appeared after the recent 6.12.6 update again. Same.. Quote Link to comment
Tarnous Posted January 8 Share Posted January 8 (edited) So I guess we should wait for some kind of fix ? Edited January 8 by Tarnous Quote Link to comment
frustratedtech71 Posted January 8 Share Posted January 8 (edited) Well that is reassurring / concerning. (glad its not just my setup and something I've screwed up accidentally) I'm also showing the same docker status issue. I first thought it was all Hotio dockers but it apears to not be isolated to that repo. Plus checked the repos are up and all have pretty much been updated in the last 96 hours. Edited January 8 by frustratedtech71 added some further text Quote Link to comment
Cybernaut Posted January 9 Share Posted January 9 +1 For me, it's 6 of 14 containers on a custom network (if that matters). I was a couple updates behind. Updated to 6.12.6 to see if that would fix it, to no avail. Quote Link to comment
frustratedtech71 Posted January 12 Share Posted January 12 I'm similar in numbers 8 out of 15 all showing all are from cr.hotio.dev/<dockername> Repo does appear to be up so I'm assuming possibly incorrectly that there has been a change made upstream and all dockers will need amending, maybe Quote Link to comment
frustratedtech71 Posted January 12 Share Posted January 12 Just tried updating the docker config to use ghcr.io as opposed to cr.hotio.dev and that appears to have worked on my test 1 Quote Link to comment
Tarnous Posted January 12 Share Posted January 12 same for me only hotio's containers Quote Link to comment
frustratedtech71 Posted January 12 Share Posted January 12 From their dev page.. explains that this is now to be expected.. Time to update the docker configs. @Tarnous Quote Link to comment
Tarnous Posted January 12 Share Posted January 12 and on the Apps "store" depot has change it's now ghcr.io/hotio/sonarr, so I guess we must change this parameter Quote Link to comment
Tarnous Posted January 12 Share Posted January 12 I've change manually the depot its fix now Quote Link to comment
Tarnous Posted January 12 Share Posted January 12 weird that there is no "autoupdate" system 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.