From 0829325d213dd4f6bf6af85566cf515cfa3f243c Mon Sep 17 00:00:00 2001 From: Felix Fontein Date: Mon, 6 May 2019 17:02:42 +0200 Subject: [PATCH] fix documentation for docker_container publish_ports option (#56093) (#56100) The documentation for the docker_container publish_ports options erroneously stated that container ports must be "exposed" in order to be "published". (cherry picked from commit 5e74ecb4fdce1356c089def82cd1ac8610778969) --- lib/ansible/modules/cloud/docker/docker_container.py | 1 - 1 file changed, 1 deletion(-) diff --git a/lib/ansible/modules/cloud/docker/docker_container.py b/lib/ansible/modules/cloud/docker/docker_container.py index f5a1905c37a..be302deab00 100644 --- a/lib/ansible/modules/cloud/docker/docker_container.py +++ b/lib/ansible/modules/cloud/docker/docker_container.py @@ -486,7 +486,6 @@ options: - "Bind addresses must be either IPv4 or IPv6 addresses. Hostnames are I(not) allowed. This is different from the C(docker) command line utility. Use the L(dig lookup,../lookup/dig.html) to resolve hostnames." - - Container ports must be exposed either in the Dockerfile or via the C(expose) option. - A value of C(all) will publish all exposed container ports to random host ports, ignoring any other mappings. - If C(networks) parameter is provided, will inspect each network to see if there exists