Due to changes in the WOWZA installer,
4.3.xand later versions are installed during container startup.
- Getting started
This Dockerfile is not provided by or endorsed by Wowza Media Systems.
NOTE: By using this image you are agreeing to comply with the Wowza EULA
Wowza Streaming Engine is unified streaming media server software developed by Wowza Media Systems. The server is used for streaming of live and on-demand video, audio, and rich Internet applications over IP networks to desktop, laptop, and tablet computers, mobile devices, IPTV set-top boxes, internet-connected TV sets, game consoles, and other network-connected devices.
If you find this image useful here's how you can help:
- Send a pull request with your awesome features and bug fixes
- Help users resolve their issues.
- Support the development of this image with a donation
Before reporting your issue please try updating Docker to the latest version and check if it resolves the issue. Refer to the Docker installation guide for instructions.
SELinux users should try disabling SELinux using the command
setenforce 0 to see if it resolves the issue.
If the above recommendations do not help then report your issue along with the following information:
- Output of the
docker runcommand or
docker-compose.ymlused to start the image. Mask out the sensitive bits.
- Please state if you are using Boot2Docker, VirtualBox, etc.
Automated builds of the image are available on Dockerhub and is the recommended method of installation.
Note: Builds are also available on Quay.io
docker pull sameersbn/wowza:4.1.2-8
Alternatively you can build the image yourself.
docker build -t sameersbn/wowza github.com/sameersbn/docker-wowza
Before you can start using this image you need to acquire a valid license from Wowza Media Systems for the Wowza Streaming Engine software. If you do not have one, you can request a free trial license or purchase a license from Wowza Media Systems.
Start Wowza using:
docker run --name wowza -d --restart=always \ --publish 1935:1935 --publish 8086:8086 \ --publish 8087:8087 --publish 8088:8088 \ --env 'WOWZA_ACCEPT_LICENSE=yes' \ --env 'WOWZA_KEY=xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx' \ --volume /srv/docker/wowza/data:/var/lib/wowza \ --volume /srv/docker/wowza/log:/var/log/wowza \ sameersbn/wowza:4.1.2-8
--env WOWZA_ACCEPT_LICENSE=yes parameter in the above command indicates that you agree to the Wowza EULA.
Point your browser to http://localhost:8088 and login using the default username and password:
Refer to the wowza quickstart guide to get started with Wowza.
For Wowza to preserve its state across container shutdown and startup you should mount a volume at
The Quickstart command already mounts a volume for persistence.
SELinux users should update the security context of the host mountpoint so that it plays nicely with Docker:
mkdir -p /srv/docker/wowza chcon -Rt svirt_sandbox_file_t /srv/docker/wowza
At first run the Wowza configuration files, among other things, will be copied into this location. You can manually edit these configurations if required.
The Wowza logs are populated in
/var/log/wowza. You can mount a volume at this location to easily access these logs and/or perform log rotation.
Alternatively you can also use
docker exec to tail the logs. For example,
docker exec -it wowza tail -f /var/log/wowza/wowza/wowzastreamingengine_access.log
To upgrade to newer releases:
Download the updated Docker image:
docker pull sameersbn/wowza:4.1.2-8
Stop the currently running image:
docker stop wowza
Remove the stopped container
docker rm -v wowza
Start the updated image
docker run -name wowza -d \ [OPTIONS] \ sameersbn/wowza:4.1.2-8
For debugging and maintenance purposes you may want access the containers shell. If you are using Docker version
1.3.0 or higher you can access a running containers shell by starting
docker exec -it wowza bash