Comment by chmrr
14 days ago
Hey -- Zulip developer who works on the Docker images here. I'm sorry you had so much trouble; that sounds like a really frustrating experience!
We were in the middle of a transition to a new Docker image when this news dropped. There was a short period where the new ghcr.io/zulip/zulip-server:11.5-0 image was broken (https://chat.zulip.org/#narrow/channel/31-production-help/to...) due to an overzealous Github Action which "helpfully" cleaned up the sub-images (see https://github.com/zulip/docker-zulip/pull/600). That's almost certainly what bit you when you first tried to pull. The image has been repaired and repushed, which is why pulls of it are working now.
The HTTP/HTPS complications you ran into are frustrations which we were specifically trying to address with the new image; and the documentation in https://zulip.readthedocs.io/projects/docker/ is specifically about the new image because we didn't expect new users to be starting fresh there but with the old image. For instance, the new image defaults to HTTP-only, since that's a much more common deployment mechanism with Docker these days. See https://zulip.readthedocs.io/projects/docker/en/latest/how-t...
It sounds like we need to do a better job of:
- Clarifying on the documentation it is for the ghcr.io/zulip/zulip-server images
- Updating the documentation link from the repo's README to be more explicitly the Docker Zulip documentation, and placing it more prominently
- Updating the links in the standard Zulip documentation to go to the new Docker documentation, and not to the repo's README.
I'll push those changes today.
We've got some instructions on moving to the new images (https://zulip.readthedocs.io/projects/docker/en/latest/how-t...), but because you don't have a lot of configuration set, this will mostly just be switching to our provided compose file.
If you have other questions or feedback, please drop by https://chat.zulip.org -- we're friendly, and happy to help out. :)
> If you have other questions or feedback, please drop by https://chat.zulip.org -- we're friendly, and happy to help out. :)
I recall reading that there would be no support for my setup if I'm not clobbering an entire server with the official installation script:
> If you decide to disregard our advice and use a server that hosts other services, we can’t support you
So, I'm just thoroughly confused at this point about what one would be expected to do in my situation, and how they could come to learn that.
That's intended to be about if you're using the non-Docker install on a host which hosts other services. Docker installs are very much a supported setup!