search

qdm12 / gluetun

VPN client in a thin Docker container for multiple VPN providers, written in Go, and using OpenVPN or Wireguard, DNS over TLS, with a few proxy servers built-in.
https://hub.docker.com/r/qmcgaw/gluetun
MIT License
6.69k stars 330 forks source link

Feature request: Option to Disable Internal Listening Ports #2318

Open engageub opened 1 week ago

engageub commented 1 week ago

What's the feature 🧐

Hi, I would like to disable internal listening ports for HTTP and ShadowSocks as I don't use them. Despite the default options being set to "off" for both HTTP and ShadowSocks, I have observed that the internal ports remain active, as evidenced by the output of the sudo docker container ls command. Given that these services are not utilized in my operational context, I believe that disabling these ports could lead to a more efficient allocation of resources.

As we rely extensively on container-to-container networking and deploy multiple instances of these containers, even minor adjustments can yield significant improvements in resource utilization and overall performance. Therefore, I am keen to explore any available options to disable these listening ports.

I would greatly appreciate your guidance on how to achieve this objective or any insights you may have regarding the best practices for optimizing our container network setup in this regard.

Thank you

Extra information and references

No response

github-actions[bot] commented 1 week ago

@qdm12 is more or less the only maintainer of this project and works on it in his free time. Please: