Another interesting thing I’ve learnt in the past couple of weeks. How to Setup Jitsi Meet Docker Container Image. But the decision which way to go is not straight forward. Collabora online office as part of a Nextcloud instance, for example, runs happily in a container. QNAP software however isn’t your typical Debian or CentOS based install. Not that I’m against dockerized installations in general. For this we’ll be following the official Jitsi Meet Docker instructions which for the most part is pretty simple. Much easier in the standard installation. Also, I didn’t manage to get performance logging working as this also has to be done inside one of the containers. There are no environment variables and no shared directories where to put such things. The apt package manager will use this GPG key to validate the packages that you will download from the Jitsi repository. See below if you are interested in running test images. First, download the Jitsi repositories GPG key using wget command. The second reason I wasn’t too happy with the Docker version is that adapting things like adding an imprint and a privacy policy to the front page is not straight forward in the dockerized Jitsi installation approach. In order to quickly run Jitsi Meet on a machine running Docker and Docker Compose,follow these steps: 1. This is the hostname that will appear in the web browser address bar when attendees join your video conference. During the installation, you need to enter a hostname for your Jitsi instance. sudo apt update sudo apt install jitsi-meet. Even simpler than using containers! This makes me wonder why there’s a dockerized version of the installation when it is even easier to install it via an apt repository!? Beats me… Next, update local package index and install Jitsi Meet on Ubuntu. In the end, my solution was not to use Docker containers at all but to install Jitsi-meet from Jitsi’s own apt repository. That really ruins your day if that happens during a live demo.īut I had a day to find a fix. I turned out that Jitsi was updated which in turn broke the Docker container setup. In the last dry run the day before, the installation procedure started to royally fail. As lots of things can go wrong in a live demo I really wanted to be prepared so I did a couple of dry-runs. To give back to the community, I wanted to do a live demo on how to install Jitsi-Meet on a server at the first Divoc conference “Hidden Service”. The need for an alternative emerged out of the blue. However, there were two problems that prompted me to search for another solution in a hurry. The Docker script sets up a couple of Docker containers that encapsulate the different programs required to run the Jitsi-meet server such as the web server, the xmpp server and other stuff. I searched around a bit and found a simple way to install it via a docker-compose script. Before I installed my first Jitsi server I thought that it must be quite a complicated affair.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |