You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Monika (Jira)" <ji...@apache.org> on 2020/04/02 14:04:00 UTC

[jira] [Commented] (OPENMEETINGS-2216) Recordings is not converted to mp4 when KMS is running as Docker container

    [ https://issues.apache.org/jira/browse/OPENMEETINGS-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073758#comment-17073758 ] 

Monika commented on OPENMEETINGS-2216:
--------------------------------------

I tried  running apache/openmeetings:min-5.0.0-M3 and KMS as separate docker containers. I can see KMS has created '.webm' file in it's container file system.. But I can't see '.mp4' in OM's docker container. How can it be possible without docker cp command? How can process of one container access file of another container?

> Recordings is not converted to mp4 when KMS is running as Docker container
> --------------------------------------------------------------------------
>
>                 Key: OPENMEETINGS-2216
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2216
>             Project: Openmeetings
>          Issue Type: Test
>          Components: Recordings
>    Affects Versions: 5.0.0-M3
>            Reporter: Monika
>            Assignee: Maxim Solodovnik
>            Priority: Blocker
>
> I wanted to know that when KMS is running as Docker container and openmeetings is running in traditional way, i .e Extracting openmeetings archive.
> How can 'nobody' user access '.webm' file from the Docker container and convert same into MP4 with ffmpeg installed on  host machine.
> I have this question because in KMS docker container '.webm' is getting created but same 'mp4' file is not generated in host file system, which is practically correct because container is equivalent to light weight VM running on host and 'nobody' user doesn't have access to read file from container file system.
> Please help me out with this as I can't access my recordings.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)