##### SUMMARY
`docker_container` should so some sanity checks that not two volumes / mount points use the same target inside the container, so that especially when recreating containers, they won't be destroyed first before recreating fails.

This becomes more important once #49808 is merged.

##### ISSUE TYPE
- Bug Report

##### COMPONENT NAME
docker_container

##### ANSIBLE VERSION
```
2.8.0
```

- 'Configure a check that is run to determine whether or not containers for this service are "healthy".
        See the docs for the L(HEALTHCHECK Dockerfile instruction,https://docs.docker.com/engine/reference/builder/#healthcheck)
        for details on how healthchecks work.'
      - 'I(interval), I(timeout) and I(start_period) are specified as durations. They accept duration as a string in a format
        that look like: C(5h34m56s), C(1m30s) etc. The supported units are C(us), C(ms), C(s), C(m) and C(h)'
    type: dict
    suboptions:
      test:
        description:
          - Command to run to check health.
          - Must be either a string or a list. If it is a list, the first item must be one of C(NONE), C(CMD) or C(CMD-SHELL).
        type: raw
      interval:
        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: