##### SUMMARY
If there's currently a container with image `repo/name:tag1` running (or created), and I change the `docker_container` image tag to `repo/name:tag2` (where this image hasn't been pulled yet), `docker_container` will not notice that the image changed and will not recreate the container.

##### ISSUE TYPE
- Bug Report

##### COMPONENT NAME
docker_container

##### ANSIBLE VERSION
```paste below
2.9.0
```

description:
          - 'Time between running the check. (default: 30s)'
        type: str
      timeout:
        description:
          - 'Maximum time to allow one check to run. (default: 30s)'
        type: str
      retries:
        description:
          - 'Consecutive failures needed to report unhealthy. It accept integer value. (default: 3)'
        type: int
      start_period:
        description:
          - 'Start period for the container to initialize before starting health-retries countdown. (default: 0s)'
        type: str
    version_added: "2.8"
  hostname:
    description:
      - Container hostname.
    type: str
  ignore_image:
    description:
      - When C(state) is I(present) or I(started) the module compares the configuration of an existing
        container to requested configuration. The evaluation includes the image version. If
        the image version in the registry does not match the container, the container will be
        recreated. Stop this behavior by setting C(ignore_image) to I(True).
      - I(Warning:) This option is ignored if C(image) or C(*) is used for the C(comparisons) option.
    type: bool
    default: no
    version_added: "2.2"