-
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
Idempotence test failure on the docker_compose_v2_pull
#813
Comments
Which Docker Compose version are you using? Also what's the stderr output of the supposedly idempotent run? |
The latest version. Currently
Play: - name: Pull images for Docker Compose project
community.docker.docker_compose_v2_pull:
project_src: /path/to/project
register: pull_output
- name: Show pull results
ansible.builtin.debug:
var: pull_output
- name: Pull images for Docker Compose project [2 pass]
community.docker.docker_compose_v2_pull:
project_src: /path/to/project
register: pull_output_2
- name: Show pull results [2 pass]
ansible.builtin.debug:
var: pull_output_2
version: "3"
services:
web:
image: ghcr.io/deadnews/deadnews-template-go:2.0.3@sha256:2d66ff9a4d36b3682b2f94ec7a575d3d2e6744ac678ecfc2b82b58200aa6f845 Output: "pull_output": {
"actions": [
{
"id": "web",
"status": "Pulling",
"what": "service"
}
],
"changed": true,
"failed": false,
"stderr": " web Pulling \n web Pulled \n",
"stderr_lines": [
" web Pulling ",
" web Pulled "
]
} "pull_output_2": {
"actions": [
{
"id": "web",
"status": "Pulling",
"what": "service"
}
],
"changed": true,
"failed": false,
"stderr": " web Pulling \n web Pulled \n",
"stderr_lines": [
" web Pulling ",
" web Pulled "
]
} |
Basically #803 fixed this for docker_compose_v2, I guess I'll have to fix it the same way for docker_compose_v2_pull... |
#814 should fix this. |
SUMMARY
When running
molecule test
, the idempotence test fails on the taskdocker_compose_v2_pull
.ISSUE TYPE
COMPONENT NAME
community.docker.docker_compose_v2_pull
ANSIBLE VERSION
COLLECTION VERSION
STEPS TO REPRODUCE
The text was updated successfully, but these errors were encountered: