zulip/docker-zulip
zulip/docker-zulip has 767 GitHub stars and 326 forks. GitHot measured 0 stars in 24 hours. Last checked 2026-11-15 00:43 UTC. Last push 2026-11-13.
측정된 스타 증가
- in 24h
- 0
- in 7 days
- 기록 수집 중
- in 15 days
- 기록 수집 중
- in 1 month
- 기록 수집 중
서로 겹치는 기간의 순증가량이며 일별 합계가 아닙니다. 측정값이 없으면 비워 둡니다. 스타는 관심도를 나타내며 품질을 보장하지 않습니다.
소개
Container configurations, images, and examples for Zulip.
개발 도구README.md
OriginalZulip Docker image overview
This is the official Docker container image for running a Zulip server in production. Built images are available from ghcr.io:
$ docker pull ghcr.io/zulip/zulip-server:13.1-0
Current Zulip version: 13.1
Current Docker image version: 13.1-0
[!NOTE] A previous packaging of Zulip for Docker still exists on Docker Hub, as zulip/docker-zulip. That version will continue to be supported through the end of the Zulip Server 11.x series. See the upgrade steps, and documentation for the older packaging.
We recommend using the Docker image if your organization has a preference for deploying services using Docker. Deploying with Docker moderately increases the effort required to install, maintain, and upgrade a Zulip installation, compared with the standard Zulip installer.
Prerequisites
To use this image, you need the following:
- An installation of Docker and Docker Compose, or a Kubernetes runtime engine.
- We recommend at least 2GB of available RAM for running a
production Zulip server; you'll want 4GB if you're building the container
(rather than using the pre-built images). If you're just testing and/or aren't
expecting a lot of users/messages, you can get away with significantly less
especially for the
postgres,memcached, etc. containers, because Docker makes it easy to sharply limit the RAM allocated to the services Zulip depends on, like Redis, memcached, and PostgreSQL (at the cost of potential performance issues).
This project doesn't support docker-rootless or uDocker; Zulip needs root
access to set properties like the maximum number of open file descriptions via
ulimit (which is important for it to handle thousands of connected clients).
Documentation
See Docker deployment documentation.
Release notes
Image release notes are in CHANGELOG.md; the Helm
chart has its own changelog at
helm/zulip/CHANGELOG.md.