Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Option to Disable Internal Listening Ports #2318

Open
engageub opened this issue Jun 12, 2024 · 1 comment
Open

Feature request: Option to Disable Internal Listening Ports #2318

engageub opened this issue Jun 12, 2024 · 1 comment

Comments

@engageub
Copy link

engageub commented Jun 12, 2024

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

Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant