Skip to content
This repository has been archived by the owner on May 10, 2019. It is now read-only.

Support for generic TCP VHOSTs #86

Closed
fancyremarker opened this issue May 4, 2015 · 2 comments
Closed

Support for generic TCP VHOSTs #86

fancyremarker opened this issue May 4, 2015 · 2 comments

Comments

@fancyremarker
Copy link
Member

No description provided.

@cancan101
Copy link

Because of: moby/moby#11185 if you are using Docker >= 1.7, I would suggest starting the daemon with --userland-proxy=false as it significantly reduces RAM usage.

Further, per: https://docs.docker.com/v1.7/articles/networking/#binding-container-ports-to-the-host:

When disabled, Docker uses both an additional MASQUERADE iptable rule and the net.ipv4.route_localnet kernel parameter which allow the host machine to connect to a local container exposed port through the commonly used loopback address: this alternative is preferred for performance reason.

@fancyremarker
Copy link
Member Author

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

No branches or pull requests

2 participants