Yong Tang 6106313b20 More descriptive error when running a container with a too long hostname (#21445) ... This fix tries to fix issues encountered when running a container with a hostname that is longer than HOST_NAME_MAX(64). Previously, `could not synchronise with container process` was generated as the length of the regex check was missing. This fix covers the length check so that a hostname that is longer than HOST_NAME_MAX(64) will be given a correct error message. Several unit tests cases and additional integration test cases are added as well. This fix closes #21445. Signed-off-by: Yong Tang <yong.tang.github@outlook.com> (cherry picked from commit fa44b4e81e)		2016-03-25 13:43:07 -04:00
..
fixtures	…
opts	More descriptive error when running a container with a too long hostname (#21445)	2016-03-25 13:43:07 -04:00
compare.go	…
compare_test.go	…
config.go	…
config_test.go	…
config_unix.go	fix some typos.	2016-03-10 10:09:27 +08:00
config_windows.go	fix some typos.	2016-03-10 10:09:27 +08:00
errors.go	…
hostconfig.go	…
hostconfig_test.go	Run privileged containers when userns are specified	2016-03-14 17:09:25 +02:00
hostconfig_unix.go	…
hostconfig_windows.go	Windows libnetwork integration	2016-03-09 20:33:21 -08:00
streams.go	Replace execdrivers with containerd implementation	2016-03-18 13:38:32 -07:00