Dockerhub kaltura/server is stuck at Naos14.12.0

bort · January 18, 2021, 5:22pm

Hello fellow people,

i am experimenting with kaltura…
I did succesfully manage to get an single server installation up and running using a docker-compose file… so far so good. and i am stunned and excited to have uploaded some videos and found generally everything up and running well (few exceptions)…

The few exceptions made me want to update the installation to kaltura 16

but i found that the kaltura/server build / tag setup stopped for some reason at 14.12.0.

In what way, would you advice may I contribute to the release of more current docker image?

As i struggled with the kaltura/server image and the mysql setup… for future researchers the files i came up with:

docker-compose.yml (CAUTION: no persistance… besides mysql)

version: "2"

services:
  phpmyadmin:
    restart: unless-stopped
    image: phpmyadmin/phpmyadmin
    env_file:
      - ./mysql.env
    ports:
      - "8080:80"
  db:
    image: mysql:5.6
    restart: unless-stopped
    volumes:
      - dbdata:/var/lib/mysql
      - ./mysql.cnf:/etc/mysql/conf.d/extra.cnf
    env_file:
      - ./mysql.env
  kaltura:
    restart: unless-stopped
    image: kaltura/server
    ports:
      - "80:80"
      - "443:443"
      - "1935:1935"
      - "88:88"
      - "8443:8443"


volumes:
  dbdata:
    driver: local

mysql.cnf

[mysqld]
sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES
lower_case_table_names = 1
innodb_file_per_table
innodb_log_file_size=32M
open_files_limit = 20000
max_allowed_packet = 16M

mysql.env

#MYSQL_DATABASE=kaltura
#MYSQL_USER=kaltura
UPLOAD_LIMIT=256M
#MYSQL_PASSWORD=supersecurepassword
MYSQL_ROOT_PASSWORD=supersecurepassword

bort · January 18, 2021, 5:32pm

ah … i just am finding / reading through

github.com

kaltura/platform-install-packages/blob/Propus-16.15.0/CONTRIBUTING.md

# Contributing Code to the Kaltura Platform
Kaltura is a multi-project platform. It consists of various back-end and front-end projects, written in several programming languages using different FOSS frameworks/libraries/technologies.
This document was put together to guide you as a developer getting started with Kaltura, walk you through the different code repos and the best practices when contributing code.

## Signing the Contributor License Agreement
When you merge new code to the Kaltura Platform, we require that you sign the Kaltura Contributor License Agreement (or "CLA"). The CLA license is for your protection as a Contributor as well as the protection of the Project and its community members. It does not change your rights to use your own Contributions for any other purpose, and does not require any IP assignment of any kind.
If you're working on a Kaltura project, or can clearly claim ownership of copyright in what you'll be contributing to the project, the CLA will ensure that your contributions are protected and that the project will forever remain free to be used and modified by the global community. 

As references, we encourage reviewing other known projects and their respective CLAs - 
* [The Apache Software Foundation](http://www.apache.org/licenses/#clas).
* [The Fedora Project](https://fedoraproject.org/wiki/Legal:Fedora_Project_Contributor_Agreement).
* [Ubuntu, Canonical Projects](http://www.canonical.com/contributors).
* [MongoDB](http://www.mongodb.com/legal/contributor-agreement).

Please [CLICK HERE TO SIGN](https://agentcontribs.kaltura.org) the Kaltura CLA digitally using your GitHub account. 
You can also [download the Kaltura CLA in PDF format](http://knowledge.kaltura.com/node/1235/attachment/field_media), sign it and email to [community@kaltura.com](mailto:community@kaltura.com).

## Which Repositories Should I Contribute To?
The main repos are:

This file has been truncated. show original

i guess thats my answer…

althought

the link to the mentioned contract is broken

links to:
http://agentcontribs.kaltura.org/agreements/KalturaCommunity/platform-install-packages

jess · January 21, 2021, 1:44pm

Hello @bort,

Thank you for your report about the broken link. We’ll take care of it. The correct href is https://agentcontribs.kaltura.org/.

Cheers,

bort · January 21, 2021, 2:19pm

Thank you @jess,

i have some follow up observations (leaving them here, as it relates to docker and possibly helps others)

I managed to build a updated docker image (which is untested for now) with this DockerFile

github.com

b0rt/platform-install-packages/blob/Propus-16.15.0/Dockerfile

FROM alekseychudov/centos8-systemd

MAINTAINER "Stephan Deglow" <stephandeglow@gmail.com>
ENV container docker

RUN echo "NETWORKING=yes" > /etc/sysconfig/network

# mysql (skipping as i plan to have mysql as extra service)
#RUN yum install -y mysql mysql-server
#RUN mysql_install_db
#RUN chkconfig mysqld on
#RUN service mysqld start

# facilities
# centos 8 ships with chronyd (replacing ntp)
RUN yum install -y postfix chrony wget dnf dnf-plugins-core yum-utils httpd systemd
RUN chkconfig postfix on
RUN chkconfig chronyd on
RUN sed -i 's@^inet_protocols = all@inet_protocol = ipv4@g' /etc/postfix/main.cf
RUN systemctl enable postfix

This file has been truncated. show original

the problematic sections have been lines 36 to 43

github.com

b0rt/platform-install-packages/blob/6e50739cd28bf3b5e14ad758f2ea0466415cc724/Dockerfile#L38



# REMI REPO FOR php
RUN dnf install https://rpms.remirepo.net/enterprise/remi-release-8.rpm -y
RUN dnf module reset php

# 7.2 is recomended for stability as the php7.4 port is fresh
RUN dnf module install php:remi-7.2 -y

# kaltura
RUN dnf install http://installrepo.kaltura.org/releases/kaltura-release.noarch.rpm -y
# kaltura-server requires kaltura-front which requires kaltura-sshpass
# for now kaltura-sshpass ist not present in noarch path http://installrepo.kaltura.org/releases/16.15.0/8/noarch/
# therefore we are installing it manually
RUN dnf install http://installrepo.kaltura.org/releases/16.15.0/8/x86_64/kaltura-sshpass-1.06-1.x86_64.rpm -y
# kalutra-server requres kaltura-dwh which requires kaltura-pentaho
# for now kaltura-pentaho in not present in noarch path http://installrepo.kaltura.org/releases/16.15.0/8/noarch/
# therefore we are installing it manually
RUN dnf install http://installrepo.kaltura.org/releases/16.15.0/8/x86_64/kaltura-pentaho-4.2.1-2.x86_64.rpm -y

# update everything to be current
#RUN yum config-manager --set-enabled powertools

i am not sure if one is aware that the packages ‘kaltura-sshpass’ and ‘kaltura-pentaho’ are not available in the noarch repo (RPM based repos are not my usual landscape to navigate)

so basically the installation failed because of those missing packages… which is odd, since the install instructions do not mention those but are referencing the noarch repo

Kind regards,

bort · January 22, 2021, 11:11am

Hi,

i just wanted to share my progress …
i did manage to have a running all-in-one docker based on centos8 using a systemd base image (which is 3rd party …see dockerfile)

A word of caution… my experiment is just for research purpose and i am leaning to the ‘cluster’ way of installing and running kaltura…

however the current roadblock ist kaltura-shpinx … this is what i am getting after running the install script.
MY guess ist that kaltura-sphinx needs a local MYSQL (or mariadb, or percona etc) to connect to…
but i am not sure… whith the official kaltura/server container and the mentioned docker-compose.yml the setup ran fine (although i did not check the sphinx functionality specifically)

Checking connectivity to needed daemons...
Connectivity test passed:)
ERROR: Couldn't connect to Sphinx with mysql -h127.0.0.1 -P9312.
Please check your setup and then run /opt/kaltura/bin/kaltura-db-config.sh again.

jess · January 22, 2021, 11:19am

Hi @bort,

What version of the mysql-client do you have? You need one comptible with 5.5. Same is true for the mysql-server. This is why the doc recommends Percona. RHEL/CentOS 8 has a newer MariaDB version in its official repos, one that is sadly incompatible with the Kaltura Server. Please see https://github.com/kaltura/platform-install-packages/issues/638

bort · January 22, 2021, 11:22am

Hi @jess,

yes thank you for the tip! … then it is reasonable that it fails… i am on v8 for the client

[root@127a8e96b814 /]# mysql --version
mysql  Ver 8.0.21 for Linux on x86_64 (Source distribution)

bort · January 27, 2021, 10:39am

for future me and readers:
i then went back to a centos7 based Base Image (see the Dockerfile in my repo)

it’s basically working okay to evaluate and test kaltura out…
but its far from ‘production ready’

here is the docker-compose.yml for now (!no persistance besides mysql)

version: "3"

services:
  phpmyadmin:
    restart: unless-stopped
    image: phpmyadmin/phpmyadmin
    env_file:
      - ./mysql.env
    ports:
      - "8080:80"
  db:
    image: percona:5.5
    volumes:
      - dbdata:/var/lib/mysql
      - ./mysql.cnf:/etc/mysql/conf.d/extra.cnf
    env_file:
      - ./mysql.env
  kaltura:
    image: b0r7/kaltura-server
   # used for systemd
    tmpfs:
      - /run
      - /tmp
    volumes:
      - /sys/fs/cgroup:/sys/fs/cgroup:ro
    # end used for systemd
    ports:
      - "80:80"
      - "443:443"
      - "1935:1935"
      # monit port 2812 https://github.com/kaltura/platform-install-packages/issues/590
      - "2812:2812"
      - "88:88"
      - "8443:8443"

volumes:
  dbdata:
    driver: local

bort · February 2, 2021, 2:07am

Hello there.

small update on my endevours:

I refined the Dockerfile a bit and pulled and deployed the kaltura-server with it recently

cons:

its huge (1.47 GB compressed / Naos 14.12.0 is 1.1GB)
Dockerfile could be optimized (e.g. remove dnf)
systemd and required volume mounts (requires linux based host)
should contain ‘don’t use in production’

pros:

after filling out install script answers… fully working
- as far as i can tell… analytics feature looks amazing!
fast to setup recent kaltura CE serving
- presumed docker knowledge
Dockerfile => install recipe for CentOS7
- at least a handy suggestion, the Dockerfile is based on the official install instructions
Base for evaluation / demos / testing (e.g. make it php7.4 by ENV VAR ?!)

todo:

testing behind a reverse-proxy (easy SSL e.g. traefik)
properly install ‘mysql-server’
- The Dockerfile installs mysql-community-server but install.sh complains anyway
- to be a propper ‘drop-in’ update of kaltura/server it should work ‘all-in-one’ as before
validate the assumption of it requiring linux hosts
persistence (my initial tryouts didn’t succeed)
remove dnf (use rpm command)
make a deb based version
make a docker-compose based version of the cluster install as the repo server-cluster-container-install seems stale but my feeling is docker-compose based install would clarify a lot of ‘first contact’ questionmarks