Latest matrix docker images are broken reddit / selfhosted ---------------------------------------------------------------------- xayon · 2023-12-13 19:44 Just a heads up. If you're like me, and have a self hosted synapse server using :latest, with a watchtower that auto-updates daily, your synapse server will probably have broken by now. If you still can, don't use latest for a while. Apparently, after the migration to element-hq ( [https://matrix.org/blog/2023/11/06/future-of-synapse- dendrite/](https://matrix.org/blog/2023/11/06/future-of-synapse- dendrite/) ) maintenance, they've broken all setups that use the old git repo (and images)... This, IMHO, is a way too-aggressive approach: [https://github.com/matrix-org/synapse/commit/e1f8440c8959719a417fbf1b dda11406cfdf523d](https://github.com/matrix- org/synapse/commit/e1f8440c8959719a417fbf1bdda11406cfdf523d), breaking existing setups on a "updated readme commit. There's an open "issue" that has not been taken seriosly here: [https://github.com/element- hq/synapse/issues/1](https://github.com/element-hq/synapse/issues/1) ---------------------------------------------------------------------- ElevenNotes · 2023-12-13 20:48 I preach this since day one: **Do not use the :latest tag on any FOSS!!!!!**, for exactly that reason. I myself make containers and don’t even deploy :latest, only :stable and versioned tags. If you use :latest and auto update all your images, that’s on you, and you only. ---------------------------------------------------------------------- xayon · 2023-12-13 21:01 I'm not complaining on the breaking itself, I know I use latest, I do it on good conscience, and I quite like testing bleeding edge software. I'm in for the game, and I didn't say otherwise. I just gave a heads-up for any that could have issues. I just promptly reverted to 1.98.0 and that made it. My concern, and the only thing I said (that it's a too agressive approach), is that the breaking code change was introduced in a "Updated readme" commit. So, before jumping to conclussions and being that offensive: \- There's no entry for that in the changelog (in fact, it's obscured in an incorrect commit message) \- They didn't announce anywhere a deprecation of the old repo (and much less \*before\* they have docker images ready). \- I stated specifically that I had read the announcements, and even the commit history. I'm quite familiar with its docs overall. So, instead of rtfm, please rtfp. Thanks ---------------------------------------------------------------------- ElevenNotes · 2023-12-13 21:12 No, this is 100% on you for updating with :latest. They announced it in November! If you don’t pay attention to the FOSS you are using, you can’t blame the FOSS for making braking changes like forking the repo over to element. ---------------------------------------------------------------------- thekrautboy · 2023-12-13 21:25 Must be a full moon tonight. ---------------------------------------------------------------------- ElevenNotes · 2023-12-13 21:27 Too soon: December 27. ---------------------------------------------------------------------- thekrautboy · 2023-12-13 21:32 Hmm i guess some dont have their time and date set correctly then. ---------------------------------------------------------------------- xayon · 2023-12-13 21:51 >They announced it beginning of November! If you don’t pay attention to the FOSS you are using, you can’t blame the FOSS for making breaking changes like forking the repo over to element. One thing is forking the repo, another is purposely introducing breaking changes in an obscure commit to force the users to change. However you look at it, that's poorly done, and aggressive. I reiterate, It hasn't been a problem for me (personal playground, anything can break), that doesn't make it more ok. Please, if you maintain any foss repo, and you're introducing breaking changes, just mark it in the commit, just out of politeness. Takes 2s and might save lots of people a few minutes. ---------------------------------------------------------------------- ElevenNotes · 2023-12-13 22:00 I already told you I don’t deploy :latest, only :stable and versioned tags, so anyone should always go read the change log and adjust their environment. ---------------------------------------------------------------------- xayon · 2023-12-13 22:27 \> I already told you I don’t deploy :latest, only :stable and versioned tags, so anyone should always go read the change log and adjust their environment. "I already told you I don't"... "so anyone should always go read". Wow, the egocentrism here is strong, "I do so, so everybody should do so". Also, the answer doesn't match what you're answering to, are you a bot? Yet, you still insist in the changelog... and I'm precisely saying that it \*\*isn't\*\*, in the changelog, can't be, as the breaking code change has been put in a commit with an "Updated readme" message. I'm really sorry but I won't keep answering you here. I have better things in which to invest my time. Good day. ---------------------------------------------------------------------- ohv_ · 2023-12-14 01:02 Immich does the same thing. ---------------------------------------------------------------------- thekrautboy · 2023-12-14 01:46 Can confirm, /u/ElevenNotes is a bot. ---------------------------------------------------------------------- partypantaloons · 2023-12-14 18:09 This is why I don’t auto-update if I’m pulling Latest