<!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->

##### SUMMARY
<!--- Explain the problem briefly below -->
With `init: true` set in the `docker_container` module, a container restarted with `docker_container` loses it network settings and is attached to the default bridge again.

##### ISSUE TYPE
- Bug Report

##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
* `docker_container`

##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
ansible 2.8.4
  config file = /home/.../.../ansible.cfg
  configured module search path = ['/home/.../.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3.7/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 3.7.4 (default, Jul 16 2019, 07:12:58) [GCC 9.1.0]
```

##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
Default configuration without any changes.

##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
* ArchLinux

##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->

<!--- Paste example playbooks or commands between quotes below -->
```yaml
---
- name: create test container
  hosts: localhost 
  gather_facts: false
  become: true
  tasks:

    - name: create a network
      docker_network:
        name: special

    - name: create a container with init set to true
      docker_container:
        name: 'test'
        state: started
        pull: true
        init: true
        image: 'traefik'
        restart_policy: always
        networks_cli_compatible: true
        networks:
          - name: special

    - name: restart test container after creation
      docker_container:
        name: 'test'
        state: started
        restart: true

...
```

<!--- HINT: You can paste gist.github.com links for larger files -->

##### EXPECTED RESULTS

The container should be restarted with the same settings and the diff should show the same as with `init: false`:
```
TASK [restart test container after creation] **************************************************
--- before
+++ after
@@ -1,4 +1,4 @@
 {
-    "restarted": false,
+    "restarted": true,
     "running": true
 }
```

`docker inspect` still shows the custom network to be configured:
```
$ docker inspect test -f "{{ .NetworkSettings.Networks }}"                                                                      
map[special:0xc00056a000]
```

##### ACTUAL RESULTS
```paste below
TASK [restart test container after creation] **************************************************
--- before
+++ after
@@ -1,4 +1,4 @@
 {
-    "init": true,
+    "init": false,
     "running": true
 }
```

`docker inspect` confirms that container has lost its custom network:
```
$ docker inspect test -f "{{ .NetworkSettings.Networks }}"                                                                      
map[bridge:0xc0001f0f00]
```
security_opts:
    description:
      - List of security options in the form of C("label:user:User")
    type: list
  state:
    description:
      - 'I(absent) - A container matching the specified name will be stopped and removed. Use force_kill to kill the container
         rather than stopping it. Use keep_volumes to retain volumes associated with the removed container.'
      - 'I(present) - Asserts the existence of a container matching the name and any provided configuration parameters. If no
        container matches the name, a container will be created. If a container matches the name but the provided configuration
        does not match, the container will be updated, if it can be. If it cannot be updated, it will be removed and re-created
        with the requested config. Image version will be taken into account when comparing configuration. To ignore image
        version use the ignore_image option. Use the recreate option to force the re-creation of the matching container. Use
        force_kill to kill the container rather than stopping it. Use keep_volumes to retain volumes associated with a removed
        container.'
      - 'I(started) - Asserts there is a running container matching the name and any provided configuration. If no container
        matches the name, a container will be created and started. If a container matching the name is found but the
        configuration does not match, the container will be updated, if it can be. If it cannot be updated, it will be removed
        and a new container will be created with the requested configuration and started. Image version will be taken into
        account when comparing configuration. To ignore image version use the ignore_image option. Use recreate to always
        re-create a matching container, even if it is running. Use restart to force a matching container to be stopped and
        restarted. Use force_kill to kill a container rather than stopping it. Use keep_volumes to retain volumes associated
        with a removed container.'
      - 'I(stopped) - Asserts that the container is first I(present), and then if the container is running moves it to a stopped
        state. Use force_kill to kill a container rather than stopping it.'
    type: str
    default: started
    choices:
      - absent
      - present