community.general/changelogs/fragments/54198-docker_container-networks.yaml

minor_changes:
- "docker_container - a new option ``networks_cli_compatible`` with default value ``no`` has been added. The default value
   will change to ``yes`` in Ansible 2.12. Setting it to ``yes`` lets the module behave similar to ``docker create --network``
   when at least one network is specified, i.e. the default network is not automatically attached to the container in this
   case."
docker_container: add networks_cli_compatible option (#54198) * Adding networks_cli_compatible option. * Move network tests into own test file. * Extend tests (for networks_cli_compatible=no). * Adding tests for networks_cli_compatible=yes. * There seems to be no way to create a container without at least one network attached. * Integrate networks / purge_networks with comparisons. * Speed up tests. * Removing double dot. * Add changelog. * Use comparisons value only if the networks option has been specified. purge_networks on the other hand also removes networks if it has not been specified. 2019-03-25 20:06:21 +01:00			`minor_changes:`
			- "docker_container - a new option ``networks_cli_compatible`` with default value ``no`` has been added. The default value
			will change to ``yes`` in Ansible 2.12. Setting it to ``yes`` lets the module behave similar to ``docker create --network``
			`when at least one network is specified, i.e. the default network is not automatically attached to the container in this`
			`case."`