search

jitsi / docker-jitsi-meet

Jitsi Meet on Docker
https://hub.docker.com/u/jitsi/
Apache License 2.0
3.01k stars 1.34k forks source link

expose containers to OpenShift #120

Open lsytnik opened 5 years ago

lsytnik commented 5 years ago

Hi,

I am trying to run jitsimeet on Openshift. Since I couldn't find an image for Openshift platform, I'm trying to load the jitsi/docker-jitsi-meet containers for the Openshift platform. Could help?

At the time of prosody container loading, the /config/data owner folder is root instead of prosody, making it impossible to create certificates.

Docker Platform /config/... drwxr-xr-x 2 root root 4096 Jul 15 16:58 certs drwxr-xr-x 2 root root 4096 Jul 11 11:32 conf.d drwxrwxrwx 3 prosody prosody 4096 Jul 18 10:30 data -rw-r--r-- 1 root root 6280 Jul 11 11:32 prosody.cfg.lua

Openshift Platform /config/... drwxr-xr-x. 2 root root 6 Jul 18 14:03 certs drwxr-xr-x. 2 root root 32 Jul 18 14:03 conf.d drwxrwxrwx. 3 root root 52 Jul 18 14:03 data -rw-r--r--. 1 root root 6280 Jul 18 14:03 prosody.cfg.lua

Openshift Platform prosody container Log:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-set-timezone: executing... [cont-init.d] 01-set-timezone: exited 0. [cont-init.d] 10-config: executing... The directory /config/data is not owned by the current user, won't be able to write files to it The directory /config/data is not owned by the current user, won't be able to write files to it mv: cannot stat '/config/data/.crt': No such file or directory mv: cannot stat '/config/data/.key': No such file or directory [cont-init.d] 10-config: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. startup info Hello and welcome to Prosody version 0.11.2 startup info Prosody is using the select backend for connection handling certmanager error SSL/TLS: Failed to load '/config/certs/meet.jitsi.key': Check that the path is correct, and the file exists. (for meet.jitsi) meet.jitsi:tls error Error creating context for c2s: error loading private key (No such file or directory)

sapkra commented 5 years ago

I'm already running these containers on OpenShift. I've added e.g. an fix-permissions.sh to each container and created a template. If you want I can clean it up and open an PR next week. When you need it right now I can also just share my changes with you.

lsytnik commented 5 years ago

Hi Sapkra,

Could you share your Pods configurations and the changes that you did to run docker-jitsi-meet images?

Thanks

saghul commented 5 years ago

If this is something easy to maintain and the broader community can benefit from it, we can include it here @sapkra. WDYT?

sapkra commented 5 years ago

OpenShift is basically based on Kubernetes. So the manifests are very similar. Since OpenShift 4 RedHat integrated support for Kubernetes Operators so my plan was to create them instead of continue using OpenShift or Helm Templates. Operators can also be used by a standalone kubernetes environment and are the future for kubernetes deployment in my opinion. It's also possible to use an Helm Operator to parse an helm template but it was added just to easely support more deployments they are already existing so it's more like an workaround I think.

@lsytnik I will cleanup my config and update it to the latest dev branch next week. So I hope you have time to wait.

lsytnik commented 5 years ago

No problem, I can wait. As Saghul commented, the community could benefit from this provision for a platform that is increasingly being used.