-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docker_compose: Cannot pull images without starting and stopping stopped containers #12
Comments
Files identified in the description: If these files are inaccurate, please update the |
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 |
Correct cmd-line analogs for docker_compose: {state: present, stopped: true, pull: true} mast be
|
* fix #12 * Create 12-correct_pull_wo_starting.yaml * Update changelogs/fragments/12-correct_pull_wo_starting.yaml Co-authored-by: Felix Fontein <[email protected]> * Update changelogs/fragments/12-correct_pull_wo_starting.yaml Co-authored-by: Amin Vakil <[email protected]> * Update docker_compose.py Co-authored-by: Felix Fontein <[email protected]> Co-authored-by: Amin Vakil <[email protected]>
SUMMARY
As @slavik57 wrote
From: ansible/ansible#31924
ISSUE TYPE
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
andstopped: true
andpull: true
should effectively dun docker-compose up --no-start --pull. And if any services are already stopped, then stop them.The text was updated successfully, but these errors were encountered: