problem when exposing the container beyond localhost

[kymilfab]

The service works perfectly using 127.0.0.1 but as soon as removing it from ports parameter or replacing with 0.0.0.0, the service does not work at all with:
hundreds of lines "Application request when we haven't used client functionality lately. Optimistically trying directory fetches again." in the logs when the container starts.
failed connection to the tor network with "Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up." any time I try to use it.

Is there a specific configuration to be able to run the container else than from local host ?

[SanujaNS]

I don't think that's a good idea to use a socks proxy over the internet cause the socks proxy does not encrypt your data. This means that your data could be intercepted and read by anyone who has access to the network. See the problem, the local network is a closed space but when you transfer over the Internet everyone has access. This isn't a heavy container, I don't think it's much of a problem to just run it locally.