Changes to --external-ip seems to be ignored when restarting coturn container - external IP seems to be cached

[woj-tek]

I'm trying to configure external IP, I tried using DETECT_EXTERNAL_IP=yes but local IP was returned. I then used --external-ip=$$(detect-external-ip) (or with explicit external IP) but each time when restarting coturn container I got:

coturn-1  | 0: (1): WARNING: NO EXPLICIT LISTENER ADDRESS(ES) ARE CONFIGURED
coturn-1  | 0: (1): INFO: ===========Discovering listener addresses: =========
coturn-1  | 0: (1): INFO: Listener address to use: 127.0.0.1
coturn-1  | 0: (1): INFO: Listener address to use: 192.168.128.3
coturn-1  | 0: (1): INFO: Listener address to use: ::1
coturn-1  | 0: (1): INFO: =====================================================
coturn-1  | 0: (1): INFO: Total: 1 'real' addresses discovered
coturn-1  | 0: (1): INFO: =====================================================
coturn-1  | 0: (1): WARNING: NO EXPLICIT RELAY ADDRESS(ES) ARE CONFIGURED
coturn-1  | 0: (1): INFO: ===========Discovering relay addresses: =============
coturn-1  | 0: (1): INFO: Relay address to use: 192.168.128.3
coturn-1  | 0: (1): INFO: Relay address to use: ::1
coturn-1  | 0: (1): INFO: =====================================================
coturn-1  | 0: (1): INFO: Total: 2 relay addresses discovered
coturn-1  | 0: (1): INFO: =====================================================

Finaly when trying out another config via docker run (so I had to bring down docker compose) with --external-ip=$$(detect-external-ip) it worked. And then when I ran docker compose it was working again but removing the option from compose and simply restarting the container didn't do anything (external IP was still maintaind) and only doing docker compose down coturn & docker compose up coturn resulted in external-ip config being properly applied.

What's more, the log prints out warning about lack of external-ip configuration even though it returns correct values.