My Jibri-Docker dont save webcam and audio in MP4 file.
Then, I access docker and run:
/etc/init.d/dbus status
I see:
“[FAIL] dbus is not running … failed!”
Then, exec:
/etc/init.d/dbus start
Now Jibri work successfull with webcam and audio.
#systemctl enable dbus
Synchronizing state of dbus.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable dbus
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit’s
.wants/ or .requires/ directory.
• A unit’s purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, …).
• In case of template units, the unit is meant to be enabled with some
instance name specified.
I follow your suggestion to create those two files , but dbus is still not running in the jibri container after restart the image. (I installed docker-jitsi-meet-stable-5765-1 on top of RHEL 8.3)
Even if I manually run /etc/init.d/dbus start , then seems dbus is up and running but the recording still failed right away.
in the /tmp/xorg.log I saw:
[235978.360] (EE) systemd-logind: failed to get session: Launch helper exited with unknown return code 1
Do this: #Stop Docker
docker-compose -f docker-compose.yml -f jibri.yml down #Get image name
grep image jibri.yml #Run build
docker build -t ??? dir
where ??? is image name and dir is directory #Start docker
docker-compose -f docker-compose.yml -f jibri.yml up -d