https://github.com/sariskaio/jibri-pulseaudio
https://github.com/sariskaio/jibri-pulseaudio
Last synced: 3 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/sariskaio/jibri-pulseaudio
- Owner: SariskaIO
- License: gpl-3.0
- Created: 2021-09-03T21:42:46.000Z (over 3 years ago)
- Default Branch: master
- Last Pushed: 2023-10-26T09:03:18.000Z (over 1 year ago)
- Last Synced: 2024-12-30T03:41:54.090Z (5 months ago)
- Language: Dockerfile
- Size: 72.3 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Docker Jibri Pulseaudio
[](https://hub.docker.com/r/prayagsingh/jibri-pulseaudio/tags) [](https://hub.docker.com/r/prayagsingh/jibri-pulseaudio)
### NOTE:
***From now onwards i.e repository tag `v1.5.0` docker image uses same tag as mentioned in the github tag name.***
#### Run Jibri using PulseAudio.
#### Please use `prayagsingh/jibri-pulseaudio:latest` for latest changes using unstable build.
#### Inbuilt Support for streaming to any rtmp server and to facebook too(one at a time).
#### Inbuilt support for rclone. use rclone to copy the recording to either google drive or S3 compatible storage. Need to add the logic in finalize.sh file.
**NOTE 1: It is mandatory to map `/dev/shm` else chrome crashes when screen-share is enabled**
### FILES
1. Use `examples/jibri.yml` with docker-compose.
2. Use `examples/stack-jibri.yml` with `docker stack deploy`.
3. Use `examples/jibri-k8s` directory to setup jibri on k8s. Use `examples/jibri-k8s/kustomization.yaml` for deployment. `Kustomize` version is `v4.0.5`.
4. Look for `update_this` and change the value accordingly. Also change `meet.example.com` with a valid URL.
***NOTE 2:*** Here I'm using `external` network in both the files. Please change it accordingly.
***NOTE 3:*** Please take the necessary steps to secure the AWS keys when using with rclone.
### SETUP tested
1. **docker-compose:** working with `1920x1080`
2. **docker-swarm:** working with `1920x1080`
3. **k8s:** working with `1280x720` resolution only. With `1920x1080`, the memory consumption reached up to 7.5 GiB and vCPU up to 6 and after 10 minutes recording crashed. With resolution `1280x720`, recording went fine. Tested in 50 minutes meeting with 3 participants and with/without screen-sharing. In order to lower down the resolution to `1280x720`, we have to change `Virtual 1920 1080` with `Virtual 1280 720` in `xorg-video-dummy.conf` file and set env variable `JIBRI_FFMPEG_RESOLUTION="1280x720"`.
**K8s resource usage with 1280x720 resolution with 3 participants in a meeting: Stable**
**K8s resource usage with 1920x1080 resolution with 3 participants in a meeting: Unstable and Crashed**
