Typically, a Docker container does not have direct access to the host machine’s network. Software running inside a Docker container would not be reachable by a client running on a machine elsewhere on the network. Docker’s software defined network must be configured explicitly to forward the incoming connection from the host machine into the server software’s Docker container. This becomes quite complicated, especially when dealing with multicast and an indeterminate range of IP addresses that the software might expect to listen on.

Instead, when running a static reflector inside a Docker container, it's recommended to configure the container to run in host networking mode (--net=host). This makes the reflector appear as though it were running natively on the host system with full access to the underlying system’s network hardware and eliminating a great deal of complexity.

Unfortunately, as of this writing, Docker supports host networking mode only on Linux. Attempting to run this software on macOS or Windows might appear to start and run successfully, but audio will not flow.

Consult the ICE Agent product guide for additional details about using Docker with the static reflector.