Repository navigation
Replies: 4 comments
|
Not sure about iptables but I have found that using asterisk containers for any kind of serious production use requires --network=host mode. |
|
Why is that? Not being able to redirect ports locks out one of the most useful feature of docker making this the only container that can run on a machine (not sure if macvlan would help here). The iptables is just a way to open them in the firewall as docker would do in bridge without the need to spawn N processes which will make the system stuck/crash |
|
Honestly not, you could use it without network_mode: host but with restricted amount of the ports (and calls) per-instance. I'll update documentaiton next week with docker and k8s setup |
|
If you don't implement it using an external script the container will definitely crash the machine though. Maybe 10 ports will not, we can try |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello,
i was wondering if there exist an easy way to pair this project with a web ui such as FreePBX or MikoPBX to make its configuration easier.
Also isn't the port specification in docker-compose suggested example
- "10000-20000:10000-20000/udp"actually killing the hosting machine when in bridge mode because it spawns 1 process for each port that needs to be open? Many other projects are using iptables (and its persistent version) to actually open the ports. Or is the intended use-case to be only used in host mode?
All reactions