September 24, 20232 yr 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?
January 2, 20242 yr 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?
January 5, 20242 yr Hi ! same here, thursday v 6.12.6 tried force update same problem Edited January 5, 20242 yr by Tarnous
January 8, 20242 yr On 1/5/2024 at 4:54 PM, cynikaly said: Hello, same problem. Appeared after the recent 6.12.6 update again. Same..
January 8, 20242 yr So I guess we should wait for some kind of fix ? Edited January 8, 20242 yr by Tarnous
January 8, 20242 yr 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, 20242 yr by frustratedtech71 added some further text
January 9, 20242 yr +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.
January 12, 20242 yr 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
January 12, 20242 yr 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
January 12, 20242 yr From their dev page.. explains that this is now to be expected.. Time to update the docker configs. @Tarnous
January 12, 20242 yr and on the Apps "store" depot has change it's now ghcr.io/hotio/sonarr, so I guess we must change this parameter
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.