Anyone run Jitsi Meet with Podman on Fedora?
People, I am interested in getting Jitsi running and like any first consideration of this sort of thing, my first thought is using Podman to do what I want - has anyone had got Jitsi Meet running satisfactorily? Thanks, Phil. -- Philip Rhoades PO Box 896 Cowra NSW 2794 Australia E-mail: phil@pricom.com.au
On Mon, Jun 14, 2021 at 12:55:59PM +1000, Philip Rhoades via Podman wrote:
I am interested in getting Jitsi running and like any first consideration of this sort of thing, my first thought is using Podman to do what I want - has anyone had got Jitsi Meet running satisfactorily?
'satisfactorily?', not sure what you mean, but it works for us. Host is Fedora 33 and we are running it rootless in 4 containers started by systemd. We have one systemd meta service which starts the other 4 jitsi containers. We are using Apache httpd as a reverse proxy in front of it for HTTPS. It took some time to set it up, but now it works without problems. Adrian
Adrian, On 2021-06-14 16:23, Adrian Reber wrote:
On Mon, Jun 14, 2021 at 12:55:59PM +1000, Philip Rhoades via Podman wrote:
I am interested in getting Jitsi running and like any first consideration of this sort of thing, my first thought is using Podman to do what I want - has anyone had got Jitsi Meet running satisfactorily?
'satisfactorily?', not sure what you mean, but it works for us. Host is Fedora 33 and we are running it rootless in 4 containers started by systemd. We have one systemd meta service which starts the other 4 jitsi containers.
We are using Apache httpd as a reverse proxy in front of it for HTTPS.
It took some time to set it up, but now it works without problems.
Excellent! Could I get images from those containers? If so, I presume there would just need to be some configuring done? - now that you have done all the hard work . . Regards, Phil. -- Philip Rhoades PO Box 896 Cowra NSW 2794 Australia E-mail: phil@pricom.com.au
Hi
Excellent! Could I get images from those containers? If so, I presume there would just need to be some configuring done? - now that you have done all the hard work . .
There are official images on dockerhub and opublished by the Jitsi project: https://github.com/jitsi/docker-jitsi-meet/ A pod definition to run all necessary containers can be found here: https://code.immerda.ch/immerda/ibox/puppet-modules/-/blob/master/ib_apache/... ~mh
mh, On 2021-06-14 21:29, mh wrote:
Hi
Excellent! Could I get images from those containers? If so, I presume there would just need to be some configuring done? - now that you have done all the hard work . .
There are official images on dockerhub and opublished by the Jitsi project:
https://github.com/jitsi/docker-jitsi-meet/
A pod definition to run all necessary containers can be found here:
https://code.immerda.ch/immerda/ibox/puppet-modules/-/blob/master/ib_apache/...
Ah thanks for that - I wonder what Adrian meant when he said: "It took some time to set it up" - if issues that needed to be solved were encountered . . P. -- Philip Rhoades PO Box 896 Cowra NSW 2794 Australia E-mail: phil@pricom.com.au
On Mon, Jun 14, 2021 at 09:41:00PM +1000, Philip Rhoades via Podman wrote:
On 2021-06-14 21:29, mh wrote:
Hi
Excellent! Could I get images from those containers? If so, I presume there would just need to be some configuring done? - now that you have done all the hard work . .
There are official images on dockerhub and opublished by the Jitsi project:
https://github.com/jitsi/docker-jitsi-meet/
A pod definition to run all necessary containers can be found here:
https://code.immerda.ch/immerda/ibox/puppet-modules/-/blob/master/ib_apache/...
Ah thanks for that - I wonder what Adrian meant when he said: "It took some time to set it up" - if issues that needed to be solved were encountered . .
I do not really remember all of it anymore. We wanted to run rootless and behind an existing reverse proxy. That made it more complicated. We first had a pod, but that did not work rootless. There were a couple of problems with how networking is setup and what we wanted. We are now using host networking. We also wanted to make it available at example.com/jitsi and spent too much time with it until we decided it is easier to run in with a dedicated domain name. Then we did not want to use lingering to start the systemd services as non-root. We are now using root systemd but with 'User=jitsi' which is also not recommended as far as I know. So there were different things that slowed us down. We somehow solved everything, but I cannot remember what we changed. It is definitely not reproducible from my side, but it is possible to make it work. Adrian
participants (3)
-
Adrian Reber -
mh -
Philip Rhoades