Overview

this guide describes how to build and use docker containers to deploy zixi broadcaster and zixi edge compute note that zixi edge compute uses the same installer and executable code as zixi broadcaster and is only differentiated from a broadcaster by the license that is applied zixi edge compute is available for no fee to be used with zixi broadcasters or aws mediaconnect and can be downloaded and licensed from the zixi customer portal https //portal zixi com/self registration/zec for the remainder of this document, any time zixi broadcaster is mentioned the same is true for zixi edge compute docker is an open platform for developing, shipping, and running applications docker enables you to separate your applications from your infrastructure so you can deliver software quickly docker provides the ability to package and run an application in a loosely isolated environment called a container the isolation and security allow you to run many containers simultaneously on a given host containers are lightweight because they don’t need the extra load of a hypervisor, but run directly within the host machine’s kernel this means you can run more containers on a given hardware combination than if you were using virtual machines you can even run docker containers within host machines that are themselves virtual machines! for containers running software that makes heavy use of ports for web uis or data transfer, you do need to consider your port mapping or ip routing strategies so that all containers on the host are accessible from the outside world for example, for broadcaster, you might map 4444 to 14444 for docker #1 and 24444 for docker #2 and 34444 for docker #3, etc , and do the same for for ports 2088, 2077, etc then you have to tell senders/receivers to use the new ports instead of the standard zixi ports for more information on docker, please refer to what is docker https //docs docker com/get started/overview/ ? this document assumes you have a basic understanding of the docker ecosystem and have docker already installed on a host also, this document assumes you are using a linux host for docker although that is not necessarily required configuration and license persistency this document and the docker image built by the included example dockerfile demonstrates how to build and run a zixi broadcaster on an arm64 system the docker container launched from this example does not keep the broadcaster configuration and license persistent if the docker container is stopped and then started again a similar document demonstrates building and running a zixi broadcaster on an x86 64 system and the example dockerfile and docker run procedure described in that document does demonstrate having the configuration and licensing of the zixi broadcaster remain persistent when the container is removed and a new container is started notes on using a docker image on amazon linux 2023 if the docker image is running on amazon linux 2023, you may see warnings when the broadcaster starts up because it attempts to obtain hardware and system information that are not available from within the container this does not affect the operation of the broadcaster below are some typical warnings that appear and the specific causes warning cause can't read memory from no direct hardware memory access in container /dev/memsnmpget command not found snmp tools not in the container image systemd / failed to connect to bus no systemd inside a container (pid 1 is not systemd) network scripts/route ` not found amazon linux 2023 doesn't use legacy network scripts lspci unable to load libkmod resources no kernel module access from inside container get nic unary operator expected nic detection script getting unexpected output