How jitsi/docker-jitsi-meet works
Purpose and Entry Points
This repository builds and composes Docker images for a self-hosted Jitsi Meet videoconferencing deployment. The primary operational entry point is docker-compose.yml; operators supply environment-specific settings from env.example and may generate credentials with gen-passwords.sh. Optional Compose overlays enable features such as recording, SIP, observability, and whiteboarding.
Image Foundation and Runtime Model
A layered image hierarchy centralizes OS and Java dependencies: base/Dockerfile provides the shared Debian-oriented base, while base-java/Dockerfile adds the Java runtime required by Jitsi backend services. Each service image adds packaged software, defaults, and an s6-overlay process graph. The s6 config-generation stage is a key boundary: container environment is rendered into runtime configuration before service startup.
Browser Client and Edge Proxy
The web container is the client-facing HTTPS endpoint and static Jitsi Meet host, with Nginx routing browser traffic and supporting TLS/ACME renewal and optional JAAS provisioning. Core paths: web/Dockerfile, web/rootfs/defaults/meet.conf, and web/rootfs/etc/s6-overlay/scripts/nginx. Browser clients connect here, then establish signaling and media sessions with the internal Jitsi services.
XMPP Signaling and Identity
Prosody is the XMPP control plane: it authenticates service identities, hosts conference/brewery/visitor domains, and coordinates room presence. Its startup graph includes configuration, SASL authentication, optional registration setup, then Prosody itself. Core paths: prosody/Dockerfile, prosody/rootfs/defaults/prosody.cfg.lua, and prosody/rootfs/defaults/conf.d/jitsi-meet.cfg.lua. This is the principal signaling boundary between clients and Jicofo/JVB/Jigasi/Jibri service accounts.
Conference Orchestration and Media
Jicofo allocates and manages conferences based on XMPP state; JVB transports and bridges real-time audio/video among participants. Both are JVM services configured from defaults and supervised by s6. Core paths: jicofo/Dockerfile, jicofo/rootfs/defaults/jicofo.conf, jvb/Dockerfile, and jvb/rootfs/defaults/jvb.conf. Control flow is broadly client/Web → Prosody → Jicofo, with Jicofo coordinating JVBs through brewery XMPP channels; media flows directly between endpoints and JVB over WebRTC.
Telephony, Recording, and Transcription Extensions
Jigasi connects SIP callers and transcription integrations to Jitsi conferences; Jibri provides browser-based recording/streaming, requiring Xorg, IceWM, PulseAudio, and Chromium before its Jibri process. Both may run an autoscaler sidecar. Core paths: jigasi/Dockerfile, jigasi/rootfs/defaults/sip-communicator.properties, jibri/Dockerfile, and jibri/rootfs/etc/s6-overlay/s6-rc.d/40-jibri/run. Feature overlays include jigasi.yml, jibri.yml, and transcriber.yml.
Observability and Optional Infrastructure
Compose overlays attach metrics, logs, traces, and RTC analytics without changing core images. Prometheus configuration is under prometheus/prometheus.yml; Grafana/Loki/OpenTelemetry assets are under log-analyser/otel-collector-config.yaml and log-analyser/loki/conf/loki-config.yaml; tracing uses Alloy and Tempo in tracing/alloy/config.alloy and tracing/tempo/tempo.yaml. RTCStats integration can depend on MongoDB and LocalStack definitions in rtcstats/mongodb/mongodb.yml and rtcstats/localstack/localstack.yml.
Delivery
Images are published to GitHub Container Registry, with stable and daily unstable release workflows. Build/release automation is rooted in .github/workflows/ci.yml, .github/workflows/release-stable.yml, and release.sh.
Main entry points: docker-compose.yml Docker Compose · prosody/Dockerfile Prosody · web/Dockerfile Web / Nginx · jicofo/Dockerfile Jicofo
Components 19
Image stack
Layered service images and runtime configuration.
- Base image · Shared Debian-oriented image foundation.
base/Dockerfile - Java base image · Shared JVM foundation for backend services.
base-java/Dockerfile - s6 config rendering · Renders container environment into runtime configuration before startup.
Conference core
Client delivery, signaling, orchestration, and media.
- Web / Nginx · Serves Jitsi Meet, HTTPS, routing, and optional ACME/JAAS.
web/Dockerfile - Browser clients
- Prosody · Authenticates service identities and hosts conference domains.
prosody/Dockerfile - Jicofo · Allocates and manages conferences from XMPP state.
jicofo/Dockerfile - JVB · Bridges real-time WebRTC audio and video.
jvb/Dockerfile
Optional media services
Telephony, recording, and transcription overlays.
- Jigasi · Connects SIP callers and transcription integrations.
jigasi/Dockerfile - Jibri · Runs Chromium-based recording and streaming.
jibri/Dockerfile - Feature overlays · Enables Jigasi, Jibri, and transcription services.
jigasi.yml
Observability
Optional metrics, logs, traces, and RTC analytics.
- Prometheus
prometheus/prometheus.yml - OTel / Loki
log-analyser/otel-collector-config.yaml - Alloy / Tempo
tracing/alloy/config.alloy - RTCStats infrastructure · Optional MongoDB and LocalStack-backed RTC analytics.
rtcstats/mongodb/mongodb.yml
Delivery
CI builds and publishes container images.
- CI and releases · Builds stable and daily unstable images.
.github/workflows/ci.yml - GitHub Container Registry
Other components
- Docker Compose · Selects core services and optional feature overlays.
docker-compose.yml - Operator environment · Environment-specific settings and generated credentials.
env.example
Connections 28
- Operator environment → Docker Compose: configures
- Docker Compose → Web / Nginx: runs
- Docker Compose → Prosody: runs
- Docker Compose → Jicofo: runs
- Docker Compose → JVB: runs
- Feature overlays → Docker Compose: extends
- Base image → Java base image: foundation for
- Base image → Web / Nginx: foundation for
- Java base image → Prosody: image layer
- Java base image → Jicofo: image layer
- Java base image → JVB: image layer
- s6 config rendering → Web / Nginx: configures before start
- s6 config rendering → Prosody: configures before start
- s6 config rendering → Jicofo: configures before start
- s6 config rendering → JVB: configures before start
- Browser clients → Web / Nginx: HTTPS client
- Web / Nginx → Prosody: signaling
- Web / Nginx → JVB: WebRTC media
- Prosody → Jicofo: XMPP conference state
- Jicofo → JVB: brewery XMPP control
- Prosody → Jigasi: service identity
- Prosody → Jibri: service identity
- Docker Compose → Prometheus: optional attachment
- Docker Compose → OTel / Loki: optional attachment
- Docker Compose → Alloy / Tempo: optional attachment
- Docker Compose → RTCStats infrastructure: optional attachment
- CI and releases → GitHub Container Registry: publishes images
- GitHub Container Registry → Docker Compose: supplies images