[Bug] Multi-port mapping of coturn cause low performance of docker

[MinatoHikari]

Describe the bug
when i use 10000-20000 port mapping, the startup of container become very slow or even crashed.
after changing port settings to 10000-10100 the containers successfully run.
i tried 3 kinds of mappings: 10000-20000 10000-11000 10000-10100.
only 10000-10100 will not cause the heavy performance problem.

To Reproduce
Steps to reproduce the behavior:

1. run official docker compose file with coturn server

[Phixygamer]

This port mapping is ridiculous and lagged networking on the entire system. I also don't think most people have all 10 000 ports free.

[schlagmichdoch]

This is a problem of coturn not of PairDrop but I understand that given compose files should work well out of the box.

For once, the problem when hosting coturn as a docker is known and the docs specifically address this:

Or just use the host network directly (recommended, as Docker performs badly with large port ranges⁠)

To do that you can set the network mode to host and remove the ports parameter in the compose.yml:

  coturn_server:
    ...
    network_mode: "host"
    ...

You would help, if you could test this and report if this solves the startup problems. I'll change the documentation then.

@Phixygamer The port mapping is just an example. If you don't have these ports open you can just use different ones.
The defaults are 49152-65535. Take a look at the example config file from coturn and change it in your own turnserver.conf accordingly (here in the turnserver_example.conf)

[MinatoHikari]

i will test later

[schlagmichdoch]

Any news?

[MinatoHikari]

Any news?

works well