-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues with docker images #1
Comments
There was an announcement see https://matrix.org/blog/2023/11/06/future-of-synapse-dendrite/ |
From that same announcement.
That's definitly not a deprecation notice for the docker images. If you're going to do so that a simple docker pull will break (or, for example, an automatic docker pull...) systems, you should at least try to announce it. Current docker images are broken, that warrants an announcement (and, probably, set an element-hq docker image repo in DH o GH or both). |
It comes, specifically, from this: matrix-org/synapse@e1f8440 Wich is an "updated readme commit" that directly exits with an error instead of passing via a deprecation warning. The worst thing, is that there's no alternative yet, docker images are not being built anywhere else (as far as I could see), so we docker self-hosters are on our own till further notice. |
Until the new docker images are working, you can use the |
Yep, been using that tag since it broke. I don't think that breaking the old images before having the new ones ready is the way to go though... |
Agreed. I too hope that the new images will be ready as soon as possible. |
from this announcement
it seems like this should have been handled better given the most recent announcement from Element. |
@benniekiss Yep, from that link:
That didn't go too well... |
I'm really sorry, breaking the docker images was not intentional at all. I've posted a comment on the other issue: #2 (comment) |
cheers for the transition! and I wonder if the announcement could be placed in the old repo (since I was very confused and I guess others think so) |
Just wanted to chime in and say that I'm pretty confused by the changes that have been taken into place. Even though I can see that it was my mistake to use the latest tag of the docker image, I still was quite upset to see that my synapse server 'just stopped working' randomly.
I didn't see any form of announcement that this was gonna happen and to me it looks like this was decided from one moment to the other.
If there was an announcement, I clearly missed it though.
Cheers,
v.d.H.
The text was updated successfully, but these errors were encountered: