What it is

docker-jitsi-meet is the Docker packaging project for Jitsi Meet, a fully encrypted, open-source video conferencing solution. It provides the tools needed to run a Jitsi Meet stack on Docker with Docker Compose, so teams can host secure video meetings inside their own infrastructure. The project lives in the Jitsi ecosystem and publishes its images through the GitHub Container Registry.

The concrete problem it solves is deployment complexity. Jitsi Meet itself is a set of open-source projects, and running a working videoconferencing stack requires assembling containers, selecting image tags, and following operational guidance. This repository gives administrators a Docker-based path to install and operate the stack, with published stable and unstable tags and a link to the official installation manual. It also points users to a separate Jitsi on Kubernetes project when the target platform is a Kubernetes cluster.

Key capabilities

• Runs the Jitsi Meet stack through Docker and Docker Compose.
• Publishes container images in the GitHub Container Registry for the Jitsi organization.
• Provides stable tags for the latest stable release and dated stable releases.
• Provides unstable tags for the latest unstable release and daily unstable releases.
• Links to the official Docker installation manual for operational setup.
• Points to Jitsi on Kubernetes tools and tutorials for Kubernetes deployment.

Who uses it and how

• Self-hosted video conferencing administrators deploy Jitsi Meet on Docker hosts.
• Teams that need encrypted, open-source meetings run the stack without an account requirement.
• Operators who need predictable releases use stable tags, while preview users use unstable or daily tags.
• Kubernetes platform teams use the separate Jitsi on Kubernetes project for cluster deployment.
• Users following the handbook install the stack with Docker Compose and pull images from GitHub Container Registry.

Getting started

The typical installation path is to follow the official Jitsi Docker installation manual and run the stack with Docker Compose using images published in the GitHub Container Registry. For Kubernetes, users are directed to the Jitsi on Kubernetes project for tools and tutorials.

When to use it — and when not to

Use it when the goal is to self-host Jitsi Meet with Docker or Docker Compose and when the operator can manage image tags, the Docker runtime, and the published GitHub Container Registry images. The available description does not list a managed hosting option, bundled database, storage, SMTP setup, or paid-product replacement. The main weakness in the available facts is operational scope: Kubernetes deployment depends on a separate project, and tag selection requires the operator to choose between stable and unstable release channels.