David, Sergey, Marcel and Sam,
Thanks for your great input.
The --network=host requirement is a showstopper for me, since I intended on using Azure’s Docker container hosting (to avoid getting a full VM). If I use that, I have no control of the host network parameters, since my container would be running in a host I can’t control.
So, my best choice is a full VM… and study the possibility of having it scheduled to run only during business hours… Or maybe just let it run 24/7 and see how much it costs. Based on the minimum requirements, I guess the lightest VMs are very capable of running FreeSWITCH.
Marcel, thanks for your 2 cents — which are worth WAY more than that, especially the database tip.
Regards,
Flavio
Well, you can configure the instance to shut down at say 8pm and start again at 8am or something like that
We use Docker throughout our stack, with the exception of FreeSWITCH. You can run FreeSWITCH in docker and I'm sure for some people it will have advantages. There are a few issues I ran into:
- FreeSWITCH needs a very large number of open ports when using SIP (thousands). Docker is not designed for this and this is the reason people tell you to use host networking (that way you skip the docker port mapping system).
Hi,
Just my 2 Cents about FreeSwtich and Docker if you are interested in learning about Docker and single-machine Orchestration: