Just have tried, everything seems to be OK [1]:
Could you please try to perform docker clean-up:
docker rm $(docker ps -a -q)
docker rmi $(docker images -q)
[1]
################################################################################
# Openmeetings is up
#
# 4.0.7 2bc5acd 2018-12-28T17:10:29Z
#
# and ready to use
#
On Mon, 28 Jan 2019 at 21:13, Maxim Solodovnik <[email protected]> wrote:
> Just have checked here:
> https://bintray.com/beta/#/openmeetings/images/server
> Version seems to be 4.0.7
>
> will try to clean the cache and check logs
>
> According to 5.0.0, it will be published as soon as it will be released
> Having 2 versions is not very good idea due to huge size of the image :(
>
> On Mon, 28 Jan 2019 at 20:48, Daniel Baker <[email protected]>
> wrote:
>
>> Hi,
>>
>>
>> When I tried :
>>
>> docker run -i --rm --name om-server -p 5080:5080 -p 1935:1935
>> openmeetings-docker-images.bintray.io/server:latest
>>
>>
>> 4.6 came down.
>>
>>
>> I see you changed the docker file to pull 4.7 so I should see 4.7 ?
>>
>> A docker image with 5 would be great too.
>>
>>
>>
>> Thanks,
>>
>> Dan
>>
>>
>>
>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon>
>> Virus-free.
>> www.avast.com
>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link>
>> <#m_-8372098486582579288_m_6193824262872680039_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>
>
> --
> WBR
> Maxim aka solomax
>
--
WBR
Maxim aka solomax
