Popple2000 Posted September 7, 2019 Share Posted September 7, 2019 Hello all! So, I recently added a 10TB Parity drive(not sure if that has anything to do with this) and since then, my DOCKER tab when I click "check for updates" shows: This looked fairly normal to me since I hadn't updated my containers in a while. I ran "update all"(same outcome if I try to update individually) and all of the "pulling image" boxes looked like this: 0 b pulled every time.(aside from when there actually is an update, as it seems to be updating if one is actually available) Once I run the updated and it finishes, all of the containers show up to date, but if I run "check for updates" again, they all show as if they need to be updated once again. Thanks in advance for any help and please don't hesitate to ask if you need more information! Link to comment
Popple2000 Posted September 7, 2019 Author Share Posted September 7, 2019 2 minutes ago, BRiT said: Thanks for that, I guess I'll just wait it out. Appreciate the heads up Link to comment
BRiT Posted September 7, 2019 Share Posted September 7, 2019 There's a fix posted in there. Link to comment
Popple2000 Posted September 7, 2019 Author Share Posted September 7, 2019 Just now, BRiT said: There's a fix posted in there. I'm currently reading through the thread as you sent this - Thanks! Link to comment
Popple2000 Posted September 7, 2019 Author Share Posted September 7, 2019 5 minutes ago, BRiT said: There's a fix posted in there. Amazing! All fixed for now! Thanks so much! Link to comment
ezhik Posted September 18, 2019 Share Posted September 18, 2019 Would be nice to see this properly fixed in 6.7.3 rather than hacking up a solution. Link to comment
itimpi Posted September 18, 2019 Share Posted September 18, 2019 It is not clear if there will ever be a 6.7.3 stable release or whether the next stable release will be 6.8. Link to comment
ezhik Posted September 19, 2019 Share Posted September 19, 2019 This should fall under a maintenance release as this impacts core functionality. Link to comment
remotevisitor Posted September 19, 2019 Share Posted September 19, 2019 While I guess this fix might be rolled into the next 6.7.3 release (now that it look like there will be one to fix the database corruption issues some people have be experiencing), for now if you have the latest CA Application auto update plugin installed it will automatically apply a fix. Link to comment
JonathanM Posted September 19, 2019 Share Posted September 19, 2019 18 minutes ago, ezhik said: This should fall under a maintenance release as this impacts core functionality. The official position on this (not mine) is that since real updates do get applied, there is not an urgent issue. They say it's cosmetic only, alerting to updates that aren't there. Container needs an update? Check, update applied. Container doesn't need an update? Check, update not applied. Indication of a needed update that doesn't actually exist, so it does not get applied is not an urgent issue, as all updates are still done as needed. Link to comment
ezhik Posted September 20, 2019 Share Posted September 20, 2019 13 hours ago, jonathanm said: The official position on this (not mine) is that since real updates do get applied, there is not an urgent issue. They say it's cosmetic only, alerting to updates that aren't there. Container needs an update? Check, update applied. Container doesn't need an update? Check, update not applied. Indication of a needed update that doesn't actually exist, so it does not get applied is not an urgent issue, as all updates are still done as needed. No argument here. Cosmetics/Convenience category. Low severity. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.