We’re trying to create a production worthy Docker image, but ran into multiple problems. We’ve managed to rewrite the container so that the docker image can be customized (it’s ipv6 enabled, ssl enabled, stores config, …).
But a few things give us a bad feeling about using wowza and the docker image.
to have a successful docker image, wowza should provide customization via environment variables. Maybe it’s a good idea to let the community manage and expand the image more (with github and pull requests for example). This would be beneficial to all users using docker images. There are already a few customize docker images, but since they are third party, company policy does not allow us to use them. Any plans of either customizing or letting the community handle this?
Is there any way to manage the persistent data by means of config? I’ve managed to mount a volume with persistent data, but since the files are scattered, we had to persist a lot of directories, which are also containing config instead of persistent data. I would argue this is bad practice, but I see no other way. Is there? Can you configure wowza in order to store all persistent data on one folder on a volume, without the main config files?
Is there a way to get wowza running redundantly? After searching the internet and the forums, the answer seems to be: no. But in a production environment, I feel this is necessary. Streams should be started on all instances and when one is down or has crashed or is restarted, this should not affect the end-user. Now a stream is not even active anymore when the container is restarted. Manual (or programmatic) action is needed. This is far from optimal. Is this indeed the way it works? No alternative setups? No database, shared caches or whatever? Any plans doing this or should we provide our own backup mechanisms in the long term?
Thanks for your answers,