March 10, 20215 yr When its on it's own specific IP address (br0), all port mappings are ignored by docker itself
March 10, 20215 yr Author 3 hours ago, Squid said: When its on it's own specific IP address (br0), all port mappings are ignored by docker itself 那为什么transmission就是显示正常的，而qbittorrent就显示不正常？
March 15, 20215 yr On 3/10/2021 at 2:04 PM, jackge0323 said: 已找到问题所在，谢谢大家回复。 方便透露下具体的原因么？感谢 我也有同样的问题，特别是个别容器已经设置了host网络，却还显示有端口映射（虽然实际上没有） Edited March 16, 20215 yr by zuchuantiemo
March 16, 20215 yr Author 7 hours ago, zuchuantiemo said: 方便透露下具体的原因么？感谢 我也有同样的问题，特别是个别容器已经设置了host网络，却还显示有端口映射（虽然实际上没有） 是因为镜像作者生成镜像的时候用了EXPOSE命令导致的，如果看不习惯的话，可以在原有镜像上自己做一个镜像，即可解决这个问题。
June 19, 20242 yr 记录一下：官方解释解决文档，按这样修改可行： WEBUI_PORT variable Due to issues with CSRF and port mapping, should you require to alter the port for the web UI you need to change both sides of the -p 8080 switch AND set the WEBUI_PORT variable to the new port. For example, to set the port to 8090 you need to set -p 8090:8090 and -e WEBUI_PORT=8090 TORRENTING_PORT A bittorrent client can be an active or a passive node. Running your client as an active node has the advantage of being able to connect to both active and passive peers, and can potentially increase the number of incoming connections. This requires an open port on the host machine which might differ from container's internal one. Similarly to the WEBUI_PORT, to set the port to 6887 you need to pass -p 6887:6887, -p 6887:6887/udp and -e TORRENTING_PORT=6887 arguments to Docker.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.