Maybe a bug: use_external_ip=false inside a docker container makes it impossible to choose the host ip

[Sulfiore]

Describe the bug
I'm not sure if this could be called a bug. It's more something that we cannot configure and the use case is very rare. So in the end I hope someone can come up with a solution and that it's not something that has to be programmed.

I'm hosting livekit inside a Docker container, my host doesn't have a public IP.
Everything is offline only. When i'm using https://livekit.io/connection-test.
I get a connection error to the ip 172.X.X.X, those are docker ips, and thus aren't accessible from my external computer.

Is there a way to tell the livekit announcer which ip to give away ?
Appart from using use_external_ip = true and try to fake a STUN packet I have no idea how to proceed.

Server

• Version: [1.8.4]
• Environment: local, no internet

edit: I already have a stun and turn server using coturn for WebRTC. I just don't know how to tell livekit to use it

[cnderrauber]

you can set rtc.node_ip in the config to the desired host ip

[Sulfiore]

Oh thank you that did the trick! I couldn't find it mentioned in any documentation, i guess it is an oversight