Portainer Templates logo

Portainer Templates

Wowza Wowza

Container

Streaming

Streaming media server

Image details

Pulls: 46.6k
Architecture: amd64
Image size: 248 MB
Latest: 4.1.2-8
User: sameersbn
Created: Jun 03, 2015
Updated: 9 years ago
Status: active

Configuration

Type
Container
Platform
linux
Image
sameersbn/wowza:4.1.2-8
Ports
1935/tcp8086/tcp8087/tcp8088/tcp
Volumes
/var/lib/wowza
Env vars
WOWZA_ACCEPT_LICENSE=yesWOWZA_KEY=''

Template by mikestraney

Standalone Install

Select an install method, to see config/commands for deploying Wowza

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Wowza, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo

More install options in our documentation.

Docker Repository on Quay.io
NOTICE:
Due to changes in the WOWZA installer, 4.3.x and later versions are installed during container startup.

sameersbn/wowza:4.1.2-8

- Contributing - Issues - Installation - Quickstart - Persistence - Logs - Upgrading - Shell Access

Introduction

Dockerfile to create a Docker container image for Wowza Streaming Engine.
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.

Contributing

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

Issues

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 version and docker info commands
  • The docker run command or docker-compose.yml used to start the image. Mask out the sensitive bits.
  • Please state if you are using Boot2Docker, VirtualBox, etc.

Getting started

Installation

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

Quickstart

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

The --env WOWZA_ACCEPT_LICENSE=yes parameter in the above command indicates that you agree to the Wowza EULA.
Alternatively, you can use the sample docker-compose.yml file to start the container using Docker Compose
Point your browser to http://localhost:8088 and login using the default username and password:
  • username: admin
  • password: admin

Refer to the wowza quickstart guide
to get started with Wowza.

Persistence

For Wowza to preserve its state across container shutdown and startup you should mount a volume at /var/lib/wowza.
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.

Logs

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

Maintenance

Upgrading

To upgrade to newer releases:
1. Download the updated Docker image:
```bash docker pull sameersbn/wowza:4.1.2-8 ```
2. Stop the currently running image:
```bash docker stop wowza ```
3. Remove the stopped container
```bash docker rm -v wowza ```
4. Start the updated image
```bash docker run -name wowza -d \ [OPTIONS] \ sameersbn/wowza:4.1.2-8 ```

Shell Access

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 bash using docker exec:
docker exec -it wowza bash

References

https://www.wowza.com/legal http://www.wowza.com/products/streaming-engine

Serve Wowza on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying wowza.example.com to http://wowza:1935

Add this to your Caddyfile

wowza.example.com {
	reverse_proxy http://wowza:1935
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Published on a random port

This template exposes 1935/tcp without setting a host port, so Docker picks a random free one on every deploy.

  • Find it in the Ports column of Portainer's container list, or with docker port <container>

Image won't pull

Test the pull directly on the host: docker pull sameersbn/wowza:4.1.2-8

  • "manifest unknown" means the tag no longer exists.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Required settings are blank

WOWZA_KEY has no default value, and the app may crash or misbehave if left empty.

  • Fill it in on the deploy screen before hitting deploy.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A single container

Wowza runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.

The app image

An image is the app packed up ready to go, everything Wowza needs bundled into one download. This template pulls sameersbn/wowza:4.1.2-8, which Docker fetches once (about 248 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Wowza's comes from Docker Hub, published by sameersbn.

Version tags

The bit after the colon in the image name is the version tag. This one pins 4.1.2-8, so every redeploy gives you that exact build until you bump it yourself.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, so it runs on regular x86 PCs and servers, though not ARM boards like a Raspberry Pi.

Ports

A port is the door the app answers on. Here the app exposes a port but leaves the host side blank, so Docker picks a free one for you. It opens:

  • 1935, published on a random host port
  • 8086, published on a random host port
  • 8087, published on a random host port
  • 8088, published on a random host port

Volumes

A volume is where Wowza keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /var/lib/wowza as a volume Docker manages for you

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Wowza takes 2 of them, and one needs a value before it'll start properly:

  • WOWZA_ACCEPT_LICENSE, defaults to yes. Agree to Wowza EULA
  • WOWZA_KEY, needs a value. License key

Networking

Nothing custom is set, so Wowza sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Wowza up. Add the template list to Portainer once, then deploying Wowza is a click rather than a wall of config.