Public Repository

Last pushed: 9 months ago
Short Description
Spreed WebRTC audio/video call and conferencing server
Full Description

This Docker repository provides a Docker image for Spreed WebRTC.

The Dockerfile can be found at https://github.com/strukturag/spreed-webrtc/blob/master/Dockerfile.run - this Docker image is not an automated build to get the size of the image as small as possible. The repository has all the gear for you to recreate the image with first building an image of https://github.com/strukturag/spreed-webrtc/blob/master/Dockerfile.build and then the final image with Dockerfile.run.

You can either use a frontend proxy like Nginx to provide TLS to Spreed WebRTC and run it in production from the Docker container. The container also provides a TLS listener with an automatically created self-signed certificate on port 8443 for testing and development setups.

Run with default settings

docker run --rm --name my-spreed-webrtc -p 8080:8080 -p 8443:8443 \
       -v `pwd`:/srv/extra -i -t spreed/webrtc

Custom configuration

To use custom configuration, use the server.conf.in file as template and remove the listeners from [http] and [https] sections. Then provide that file when running the docker container as with -c parameter like this:

docker run --rm --name my-spreed-webrtc -p 8080:8080 -p 8443:8443 \
       -v `pwd`:/srv/extra -i -t spreed/webrtc \
       -c /srv/extra/server.conf

Environment variables

And last, this container checks environment variables NEWCERT and NEWSECRETS, on startup. Set those to 1 to regenerate the corresponding values on start. The current certificate and secrets are printed before startup so you can use them easily for other services. Of course, if you want to have persistent cert and secrets, the container needs to be persistent in the first place, so no --rm parameter in the example from above in that case.

Docker Pull Command
Owner
spreed

Comments (6)
nimaafraz
2 months ago

It's gets stuck on the following message and when trying to access through the browser connection is refused.
-----END CERTIFICATE-----
Creating new server secrets ...

I somehow managed to get it working once but I'm having the same problem again.

cguenther
3 months ago

Please provide also latest builds for the non-stable releases from github. In the meantime, there is a big gap between the latest and the here published stable release.

ted77
7 months ago

t works great when run with the following command :
docker run --rm --name my-spreed-webrtc -p 8080:8080 -p 8443:8443 \
-v pwd:/srv/extra -i -t spreed/webrtc

but not with the second as it claims that server.conf does not exist.

My objectives are:

Have Spreedme run at boot time
Use different ports than 8080 and 8443
only allow users logged into Nextcloud to access the Spreedme as of now anyone that knows the ip and port can access spreedme.

My OS is ubuntu 16

Any help ? thank you

barmet75
8 months ago

Thanks for sharing
Working like a charm

Bye

pietervandereems
8 months ago

Dockerfile?

nathanhourt
8 months ago

Why isn't this an automated build? :\