Docker configuration reference

This reference lists the images, hostnames, environment variables, ports, and volumes you can configure for the Wowza Streaming Engine™ (WSE) and WSE Manager Docker images. To deploy the images, see Deploy Wowza Streaming Engine with Docker.

With Docker Compose, set these options in docker-compose.yaml. With standalone containers, pass them as docker run options.

Wowza Streaming Engine

Environment variables

Set environment variables under the environment key in the Compose file, or with the --env flag in the docker run command.

environment:
    - ADMIN_PASSWORD_ENCRYPTED=true
    - ADMIN_PASSWORD=$$pbkdf2-sha512$$210000$$[salt]$$[hash]

Ports

Map container ports to the host machine in host:container format. Use the ports key in the Compose file, or the --publish flag in a docker run command. WSE uses the default ports listed in the table below. Publish only the ports your workflows use, and make sure they aren't already in use on the host.

Volumes

A volume binds a directory on the host to a directory in the container, in [host_path]:[container_path] format. Volumes persist applications, configuration, content, transcoder settings, and logs between container runs. They aren't required, but we recommend them for logs so log files don't fill the container's primary disk. Uncomment the entries in the volumes array of the Compose file as needed, or add them with the --volume flag in the docker run command. The Compose file doesn't include an entry for the logs directory, so add one if you want to persist logs.

You can mount the following WSE directories:

If a mounted conf, content, transcoder, lib, or lib-native directory is empty when the container starts, WSE copies the image's default files into it.

Add files to a WSE directory

To add files to a WSE directory without replacing its contents, mount a host directory at the same container path with .addon added to the directory name. When the container starts, WSE copies the files from the .addon directory into the matching WSE directory. For example, to add custom module JAR files to the lib directory:

volumes:
    - ./mylibs:/usr/local/WowzaStreamingEngine/lib.addon

For the lib directory, WSE first removes older versions of each JAR file when the file name includes a semantic version, such as mymodule-1.0.3.jar.

SSL/TLS

The Trial image includes an SSL certificate for wse-trial.wowza.com, which resolves to 127.0.0.1. The Trial image downloads the latest copy of the certificate each time the container starts. For Base, Slim, and VIF, configure your own certificate to stream over SSL/TLS.

WSE Manager

Environment variables

Ports

The WSE Manager container listens on the ports listed in the following table. To reach WSE Manager from outside the container, publish each port you need to a port on the host. For example, 8088:8080 exposes WSE Manager on port 8088 of the host, so you can sign in at http://localhost:8088.

Volumes

To add Tomcat configuration files to WSE Manager, such as a JKS file or a custom server.xml, mount a host directory at /usr/local/tomcat/conf.addon. When the container starts, WSE Manager copies the files into /usr/local/tomcat/conf. For example:

volumes:
    - ./wse.addon/manager/conf:/usr/local/tomcat/conf.addon
environment:
    - JKS_FILE=/usr/local/tomcat/conf/tls.jks
    - JKS_PASSWORD=[keystore-password]