Running a Container

to run a docker image in a container to maintain persistence of a zixi broadcaster’s configs when the docker container is terminated (via the docker rm command or the host system being powered off while the container is running), the broadcaster config xml, broadcaster info xml, and broadcaster lic files need to be stored on the host system so they will be available to a newly started container the approach used here is inside the docker image we create a configs directory and then symlink those three files from the broadcaster install directory, their default location, into the configs directory then we map that configs directory to the host similar to how we map the logs and files directories a caveat to this approach is upon the first time running, the broadcaster does not work with a symlink to an empty broadcaster config xml file to satisfy the broadcaster at initial startup, we copy a minimal broadcaster config xml file (see appendix b) into the configs folder on the host that is mapped to the configs folder inside the container the broadcaster will subsequently update the config file with user settings copy the config file as shown below cp broadcaster config template raspberry xml /bxconfigs/broadcaster config template xml run the image and create a new container using a run command as shown below docker run net=host volume /bxlogs\ /zixi broadcaster linux64/logs volume /bxfiles\ /zixi broadcaster linux64/files name broadcaster \<version number> zixi broadcaster \<version number> the run command has many options below is a description of the options used in this example net this option allows you to choose the type of networking used in the container with “host” mode all containers on the host share the hosts networking configuration and to access a container you would use the host’s ip address, such as 192 168 10 20 4444 for the broadcaster ui if you have multiple broadcaster containers running on the same host you would need to configure the broadcaster in each container to use a different port for the ui and different ports for zixi or other input and output protocols also, you will need to configure the firewall on the host to protect the running containers from external threats with “bridged” mode, which is the default if you do not specify the net option, each container will have its own network that exists on host the host will be able to directly communicate with the containers but any other device on the network cannot communicate with the containers unless ip forwarding is enabled see this link https //docs docker com/network/bridge/#enable forwarding from docker containers to the outside world for more information on ip forwarding on the host networking in bridged mode will be slightly less efficient than host mode because there is an additional layer of networking redirection volume this option allows you to mount directories inside the container to directories on your host system in this example we are mounting the logs directory and the files directory from the broadcaster installation directory to local folders which makes it easy to inspect logs or retrieve recordings from the broadcaster running in the container name this option gives the container a human readable name when looking at the docker process table publish this option is only valid with bridged mode networking in the dockerfile you will see that we exposed typical ports that you would use with the broadcaster however, those ports will only be exposed to the host if you also publish them in the run command with command line options on the docker run command, such as the following publish 4444 4444/tcp publish 2088 2088/udp for host mode networking, all network settings are controlled on the host itself and publish is ignored d restart unless stopped these options can be added so the docker container will automatically restart if the host system is powered off and back on mac address if the host system presents a new mac address every time it is restarted, this will invalidate the licensing and an option like mac address 02 42\ ac 11 00\ de can be used to force the same mac address every time image id – the last option is the image id which you see in the images table above upon using the docker run command, there will now be a running docker container you can see the list of all running containers using the following command docker ps the output will be similar to the following (with different ids) container image command created status ports names f8f30e025166 855f142a53a7 " /zixi broadcaster …" 21 minutes ago up 21 minutes broadcaster 16 4 44543 in host mode the ports will be empty in bridged mode the actual ports that were published will be shown in the shell window where you issued the docker run command you will see any content going to stdout and stderr inside the container on stdout of the docker run process on the host with the container running, you can log into the broadcaster web ui at port 4444 in host mode you will use the ip address of the host itself in bridged mode you can use a command like the following to see the ip address of the running container docker inspect f '{{ name}} {{ networksettings ipaddress }}' $(docker ps aq)