Docker and API map to 0.0.0.0 #8335
Replies: 2 comments
-
These settings should be mostly configurable through a configuration file. First, you should locate your "state directory". Depending on how you run your Docker container, your state directory will end up in a different folder. For example, if you follow https://tribler.readthedocs.io/en/latest/basics/docker.html#running, your state directory will end up in In the state directory, you should find the If you're looking to change your API host (TCP) to {
"api": {
...
"http_port": 8085,
"http_host": "127.0.0.1",
...
}
...
} You can do the same thing with the For libtorrent, you can only change the I think the above should work, but this is not something I play with daily. Please let me know if any of this doesn't work out. |
Beta Was this translation helpful? Give feedback.
-
@qstokkink Ooooh, it's as simple as that, it's perfect! I don't necessarily need to force the modification of tribler and/or libtorrent ports at the moment, just to make sure which ports to open and with which protocol (tcp, udp). Have a nice day |
Beta Was this translation helpful? Give feedback.
-
Docker and API map to 0.0.0.0Docker and webUI map to 0.0.0.0
Hi
On the forum, I explained that I wanted to use Tribler via docker, with strict iptables rules (default policy DROP).
In
network_mode: "host"
, Tribler and/or libtorrent attach a port to each IP ported by the host, and with X containers, I have X ports listening.It's a mess. If I'm not mistaken, these ports (3XXXX) are linked to ‘Local Peer Discovery’.
So I want Tribler to have its own docker network to isolate it.
However, I obviously can't map access to the web UI via ...
Is it possible to have an option to create a web UI that listens on 0.0.0.0 rather than 127.0.0.1 in the container, please?
To continue with my post in the forum, are the only ports to be authorised in iptables on the host really ...
in tcp and udp please?
Thank you in advance for your help
Beta Was this translation helpful? Give feedback.
All reactions