docker_compose: Cannot pull images without starting and stopping stopped containers

[abeluck]

SUMMARY

As @slavik57 wrote

Currently there is no way to pull the images without starting the containers.
When running with state:absent and pull:true it won't pull the images.
When running with state:present and pull:true and stopped:yes it will pull the images, start the containers and then stop them.
This may cause some unwanted behaviour such as volume creation if there is a local volume mapping.

From: ansible/ansible#31924

ISSUE TYPE

• Bug Report

COMPONENT NAME

docker_compose

ANSIBLE VERSION

2.x

OS / ENVIRONMENT

All

See previous discussion at ansible/ansible#31924

It is my (@abeluck) opinion that we should maintain backwards compatibility. And so state: present and stopped: true and pull: true should effectively dun docker-compose up --no-start --pull. And if any services are already stopped, then stop them.

[ansibullbot]

Files identified in the description:

• plugins/modules/cloud/docker/docker_compose.py

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

[ansibullbot]

cc @DBendit @WojciechowskiPiotr @akshay196 @chouseknecht @danihodovic @dariko @felixfontein @jwitko @kassiansun @sluther @tbouvet
click here for bot help

[sluther]

This was discussed in an old issue (ansible/ansible#31924) before all of the modules got migrated to this repository.

We discussed fixing this by addressing the issue with stopped: true where it is incorrectly starting containers that aren't running.

[tonal]

Correct cmd-line analogs for

docker_compose: {state: present, stopped: true, pull: true}

mast be

# docker-compose pull && docker-compose up --no-start