Sign inSign up

readystack/jitsi

By readystack

•Updated about 8 hours ago

Jitsi Meet: video conferencing in the browser and mobile apps. Signed; SBOM and SLSA v1 provenance.

Image
Networking
0

4.4K

readystack/jitsi repository overview

⁠Jitsi Meet

Signed: cosign SBOM: SPDX attached Provenance: SLSA v1

readystack/jitsi:stable-11248-CE-ubuntu24.04-r4

Source, recipe and records

A cosign-signed build of github.com/jitsi/jitsi-meet stable/jitsi-meet_11248 (Apache-2.0), built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Organisations and individuals who want to run their own video meetings.

Why: Jitsi Meet is open-source video conferencing that works in the browser and in mobile apps, with screen sharing, chat, polls and raise-hand, and it can be embedded in other web applications.

Use case: A school wants video lessons without sending its classes through an outside service. It runs Jitsi Meet on its own server; teachers share a meeting link, students join from a browser or the mobile app, and the teacher shares slides and runs quick polls during the lesson.

About the upstream project, written from its own description: https://github.com/jitsi/jitsi-meet⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:a6c5fd563d14a1abbfc5c6b559bd32e5332781431e5a31271c58c17078b9fc51 on 2026-11-10.

  • Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with cerodeo-v2, ce.rodeo's current rubric; scans before 2026-11-08 used cerodeo-v1) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products/jitsi⁠
  • ReadyStack release check — passed at release on 2026-11-10: no fixable critical or high vulnerability (Docker Scout and OSV), a non-root user, SBOM and provenance attached. This is ReadyStack's own test, not a Docker grade; vulnerabilities published since then are in today's result at https://readystack.dev/queue⁠.
  • Signed — cosign signature by the ReadyStack release key (fingerprint 04daa92344a52dbc) on this release's index digest sha256:a6c5fd563d14a1abbfc5c6b559bd32e5332781431e5a31271c58c17078b9fc51; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/jitsi:stable-11248-CE-ubuntu24.04-r4.
  • Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
  • Runs as a non-root user (jitsi).
  • Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

  • The current release is stable-11248-CE-ubuntu24.04-r4 — the release listed at readystack.dev. Release tags use the pattern <upstream-version>-CE-<base-os>-r<N>; the current one is signed, attested (SBOM + provenance), and is provided under the ReadyStack Agreement⁠.

  • Earlier release tags (an older version or revision in the same pattern) are superseded. They stay pullable so existing deployments can pin them, but they are no longer re-graded, and fixes appear only in newer releases: move to the current release. For a superseded release's build kit, ask support.

  • Release tags never move, so pulling the same tag again never changes the image. To be offered each new release automatically (a new revision r<N+1>, or a new upstream version), use the ReadyStack Renovate preset: https://readystack.dev/updates.html⁠

  • Any tag beginning with internal- is an engineering-pipeline artifact published for build observability. It is unsupported, may change or disappear without notice, and must not be used in production.

# ✓ current release
docker pull readystack/jitsi:stable-11248-CE-ubuntu24.04-r4

# ✗ unsupported (do not pull)
docker pull readystack/jitsi:internal-...

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/jitsi:stable-11248-CE-ubuntu24.04-r4 (the signature is recorded in the public Sigstore transparency log). Support: [email protected]⁠, as set out in the ReadyStack Agreement⁠.

⁠Deployment

Single container holding ONLY the Jitsi Meet web frontend: the browser application (built from source) served by nginx as a non-root user on port 8080, with /http-bind and /xmpp-websocket proxied to an XMPP server. It is NOT a complete Jitsi Meet: a conference also needs prosody (XMPP signalling), jicofo (conference focus) and jitsi-videobridge (the media server, UDP 10000). None of those are in this image. The environment variable names match docker-jitsi-meet's web service, so this container can replace that service in a docker-jitsi-meet deployment that supplies the other three.

docker run -d --name jitsi-web -p 8080:8080 -e XMPP_DOMAIN=meet.jitsi -e XMPP_MUC_DOMAIN=muc.meet.jitsi -e XMPP_BOSH_URL_BASE=http://xmpp.meet.jitsi:5280 readystack/jitsi:stable-11248-CE-ubuntu24.04-r4

Run it on the same Docker network as your prosody container (XMPP_BOSH_URL_BASE must reach prosody's HTTP port, 5280) and put an HTTPS reverse proxy in front of port 8080: browsers only allow camera and microphone on https pages (or http://localhost⁠).

⁠The full ReadyStack Hermetic Build Kit

The complete --network=none build kit for this image — plus admin/DB/API handbooks, the build's validation records, and its build provenance records — is a free download for any registered account at readystack.dev/products/jitsi⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:759b8528be92efe5d13aa4ba70d3b9f2a5df5ddfc8c562196ebd24325cdd8737 on 2026-11-10.

— ReadyStack · readystack.dev

Tag summary

Content type

Image

Digest

sha256:b86793433…

Size

3 MB

Last updated

about 8 hours ago

docker pull readystack/jitsi:sha256-759b8528be92efe5d13aa4ba70d3b9f2a5df5ddfc8c562196ebd24325cdd8737.att