Run BigBlueButton 2.0-beta in Docker

[Fred Dixon]

Want to run your own BigBlueButton server with a single command?

Now you can.

We've created a Docker image that lets you run a full BigBlueButton 2.0-beta server (including latest developer build of the HTML5 client) within Docker.

This means you can run BigBlueButton on Mac OS X, for example.  

This isn't intended for production; rather, it's targeting developers who want to quickly try out BigBlueButton.  With Docker, you can login to the running BigBlueButton server examine the configuration files, make changes, and see how everything works.  There are limitations: the docker image doesn't have a SSL certificate, so Chrome will give an error with accessing WebRTC, but FireFox works fine.

For documentation, see

  http://docs.bigbluebutton.org/labs/docker.html

For source to customize and build your own Docker container, see

  https://github.com/bigbluebutton/docker

The official docker image for BigBlueButton 2.0-beta is here

  https://hub.docker.com/r/bigbluebutton/bigbluebutton/

Under the hood, we are using supervisord -- a process control manager -- to coordinate the startup of all the BigBlueButton processes within a single container. Our goal wasn't to break apart BigBlueButton into separate containers (which is more the docker way), but rather to make it easy for anyone to try out BigBlueButton.

We invite you to try it out and give us your feedback.

Regards,.. Fred

--

BigBlueButton Developer

http://bigbluebutton.org/

@bigbluebutton

[vn...@yandex.com]

Regarding the SSL cert, is that impossible, or only painful?  Perhaps leave the nginx/ssl part natively hosted, and pass the ports in via the docker command-line?

All the rest sounds super-great!

I vote for proceeding in the usual docker way, and splitting it into pieces.  Then add some kubernetes magic for scalability, failover, etc. .

Oh, and continue all efforts to kill flash!  HTML5, yay..

[Fred Dixon]

Hi there,

> Regarding the SSL cert, is that impossible, or only painful? 

We'll add steps to add a SSL certificate in an update to the instructions to setup BigBlueButton under Docker.  Since our target for this is developers, using FireFox works well.

> Perhaps leave the nginx/ssl part natively hosted, and pass the ports in via the docker command-line?

Splitting up BigBlueButton into individual docker containers is possible, but we didn't want to try that for the first release.   With this first release, as we evolve the BigBlueButton architecture we can evolve the options for docker/containers as well.

Regards,.. Fred

--
You received this message because you are subscribed to the Google Groups "BigBlueButton-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-dev+unsubscribe@googlegroups.com.
To post to this group, send email to bigbluebutton-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/bigbluebutton-dev.
For more options, visit https://groups.google.com/d/optout.

[Dimitar Dimitrov]

The SSL certificate is not impossible and not painful. The problem is that it is domain and certificate specific and the image is universal, which makes it difficult to provide ready image.

I needed to do this, because of a client, which allows only SUSE installations in their environment.

What you can do is (not perfect way but working):

- define your domain and make sure it is resolvable.

- add 443 and 7443 to port mapping in the run command.

- edit the setup.sh file accordingly using the HTTPS installation instructions for bigbluebutton

this you can do in the source if you build the image from source or in the container (/root/setup.sh)

better build the image from source, you will get latest bbb 2.0

- obtain SSL proper certificate and transfer it to the container

- attach to the container

- follow the instructions for HTTPS in bigbluebutton installation document

Implement the instructions in setup.sh or do them manually, but make sure that setup.sh will not overwrite the changes

Tested and working like installed on real machine with Ubuntu 16.04

[satyakam goswami]

We invite you to try it out and give us your feedback.

i am trying to run docker using the command 

$docker run -p 80:80/tcp -p 443:443/tcp -p 1935:1935 -p 5066:5066 -p 3478:3478 -p 3478:3478/udp bigbluebutton/bigbluebutton -h 127.0.0.1

docker did not come up with the following errors https://hastebin.com/cojawihaju.diff , i am trying to run the docker command on Linux Mint 19.1 

thanks

-Satya

[Fred Dixon]

Hi Satya,

These errors are fine (we'll probably clean them up in the next update).  Note we don't recommend running BigBlueButton in production in a container, but it's good for testing, development, and understanding how BigBlueButton works.

Regards,... Fred

--

You received this message because you are subscribed to the Google Groups "BigBlueButton-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-...@googlegroups.com.
To post to this group, send email to bigblueb...@googlegroups.com.

Visit this group at https://groups.google.com/group/bigbluebutton-dev.
For more options, visit https://groups.google.com/d/optout.