Su Wang 2c4a868f64 Added API to set ephemeral port allocator range. ... Also reduce the allowed port range as the total number of containers per host is typically less than 1K. This change helps in scenarios where there are other services on the same host that uses ephemeral ports in iptables manipulation. The workflow requires changes in docker engine ( https://github.com/moby/moby/pull/40055) and this change. It works as follows: 1. user can now specified to docker engine an option --published-port-range="50000-60000" as cmdline argument or in daemon.json. 2. docker engine read and pass this info to libnetwork via config.go:OptionDynamicPortRange. 3. libnetwork uses this range to allocate dynamic port henceforth. 4. --published-port-range can be set either via SIGHUP or restart docker engine 5. if --published-port-range is not set by user, a OS specific default range is used for dynamic port allocation. Linux: 49153-60999, Windows: 60000-65000 6 if --published-port-range is invalid, that is, the range given is outside of allowed default range, no change takes place. libnetwork will continue to use old/existing port range for dynamic port allocation. Signed-off-by: Su Wang <su.wang@docker.com>		2019-10-11 18:48:07 +00:00
..
config.go	Added API to set ephemeral port allocator range.	2019-10-11 18:48:07 +00:00
config_test.go	Revert "validate network and endpoint name more strictly"	2017-02-01 18:18:17 -08:00
libnetwork.toml	TOML based Configuration support for libnetwork	2015-05-25 16:29:40 -07:00