This actually make no sense :( I always thought docker should work the same for different machines
This is my start command and first lines of the output: `docker run -i --rm --name om-server-full --expose=5443 --expose=8888 -p 5443:5443 -p 8888:8888 openmeetings-docker-images.bintray.io/server-full:latest` * Stopping MySQL database server mysqld ...done. * Starting MySQL database server mysqld ...done. OM server of type full will be run * Start Kurento Media Server * Directory '/var/log/kurento-media-server' is not owned by 'nobody' * Changed owner of '/var/log/kurento-media-server' to 'nobody' * Configure Kernel resource limits for Kurento Media Server ...done. This is the line the KMS is being started: https://github.com/openmeetings/openmeetings-docker/blob/master/scripts/om.sh#L44 Have no idea what is going on :( On Sun, 22 Sep 2019 at 01:29, YUP <[email protected]> wrote: > I checked your image, and got the same result, kurento is dead. I > gonna give up.... > > $ docker info > Client: > Debug Mode: false > > Server: > Containers: 4 > Running: 4 > Paused: 0 > Stopped: 0 > Images: 45 > Server Version: 19.03.2-ce > Storage Driver: overlay2 > Backing Filesystem: extfs > Supports d_type: true > Native Overlay Diff: false > Logging Driver: json-file > Cgroup Driver: cgroupfs > Plugins: > Volume: local > Network: bridge host ipvlan macvlan null overlay > Log: awslogs fluentd gcplogs gelf journald json-file local > logentries splunk syslog > Swarm: inactive > Runtimes: runc > Default Runtime: runc > Init Binary: docker-init > containerd version: d50db0a42053864a270f648048f9a8b4f24eced3.m > runc version: 425e105d5a03fabd737a126ad93d62a9eeede87f > init version: fec3683 > Security Options: > seccomp > Profile: default > Kernel Version: 4.19.73-1-lts > Operating System: Arch Linux > OSType: linux > Architecture: x86_64 > CPUs: 2 > Total Memory: 3.789GiB > Name: archmoodle > ID: SJE6:7KPL:M7AE:H6RE:CDR6:RK2K:Q2PQ:CD6W:DJOO:V4LZ:2ILL:NCWY > Docker Root Dir: /home/docker > Debug Mode: false > Registry: https://index.docker.io/v1/ > Labels: > Experimental: false > Insecure Registries: > 127.0.0.0/8 > Live Restore Enabled: false > > сб, 21 вер. 2019 о 19:00 Maxim Solodovnik <[email protected]> пише: > > > > `docker info` > > > > Server Version: 19.03.2 > > > > > > The image is uploaded, everything works as expected > > Just have double-checked > > `docker run -i --rm --name om-server-full --expose=5443 --expose=8888 -p > 5443:5443 -p 8888:8888 > openmeetings-docker-images.bintray.io/server-full:latest` > <http://openmeetings-docker-images.bintray.io/server-full:latest> > > > > On Sat, 21 Sep 2019 at 23:43, YUP <[email protected]> wrote: > >> > >> BTW, what version of docker do you use? > >> $ docker info > >> > >> сб, 21 вер. 2019 о 18:30 YUP <[email protected]> пише: > >> > > >> > Great, thanks! > >> > > >> > сб, 21 вер. 2019 о 18:29 Maxim Solodovnik <[email protected]> > пише: > >> > > > >> > > Well > >> > > I can upload my image to the bintray > >> > > And you can try it > >> > > Will do it tomorrow > >> > > > >> > > On Sat, Sep 21, 2019, 23:14 YUP <[email protected]> wrote: > >> > >> > >> > >> So something is wrong with Archlinux as a host machine and OM in > >> > >> docker. But it is nonsense, created image should not depend from > host > >> > >> machine and om+mysql+kurento must run the same way... > >> > >> > >> > >> сб, 21 вер. 2019 о 18:03 Maxim Solodovnik <[email protected]> > пише: > >> > >> > > >> > >> > Kurento and mysql are both started right before om > >> > >> > It is very clear from the logs > >> > >> > And both video and recording works in om :) > >> > >> > > >> > >> > On Sat, Sep 21, 2019, 22:55 YUP <[email protected]> wrote: > >> > >> >> > >> > >> >> OK. Please enter your container with running OM: > >> > >> >> > >> > >> >> docker exec -it CONTAINER_ID bash > >> > >> >> and then check whether kurento running: > >> > >> >> ps xuaw | grep kurento > >> > >> >> or > >> > >> >> service kurento-media-server status > >> > >> >> and post the result, please. > >> > >> >> > >> > >> >> > >> > >> >> > >> > >> >> > >> > >> >> сб, 21 вер. 2019 о 16:59 Maxim Solodovnik <[email protected]> > пише: > >> > >> >> > > >> > >> >> > `docker build -t om-server-full --build-arg BUILD_TYPE=full .` > >> > >> >> > `docker run -i --rm --name om-server-full --expose=5443 > --expose=8888 -p 5443:5443 -p 8888:8888 -e OM_TYPE=full -it om-server-full` > >> > >> >> > > >> > >> >> > works as expected :) > >> > >> >> > > >> > >> >> > On Sat, 21 Sep 2019 at 20:37, YUP <[email protected]> wrote: > >> > >> >> >> > >> > >> >> >> > Will provide you with the complete list of commands I run > >> > >> >> >> Thanks, it will be useful! > >> > >> >> >> > >> > >> >> >> > BTW just found this thread: > https://groups.google.com/d/msg/kurento/e93n1plA0EM/XxVVKtWSAQAJ > >> > >> >> >> > Might be useful for nginx users > >> > >> >> >> > >> > >> >> >> I'll check it. > >> > >> >> >> Regards, > >> > >> >> >> Yarema > >> > >> >> > > >> > >> >> > > >> > >> >> > > >> > >> >> > -- > >> > >> >> > WBR > >> > >> >> > Maxim aka solomax > > > > > > > > -- > > WBR > > Maxim aka solomax > -- WBR Maxim aka solomax
