You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It feels like this happens on a new, not pulled yet images. After second run these warning are gone.
EXPECTED RESULTS
No warnings.
ACTUAL RESULTS
[WARNING]: Cannot parse event from line: '4f4fb700ef54 Waiting'. Please report this at https://github.com/ansible-collections/community.docker/issues/new?assignees=&labels=&projects=&template=bug_report.md
[WARNING]: Cannot parse event from line: '238022553356 Downloading 541B/541B'. Please report this at https://github.com/ansible-collections/community.docker/issues/new?assignees=&labels=&projects=&template=bug_report.md
[WARNING]: Cannot parse event from line: '972e292d3a60 Downloading 106kB/10.43MB'. Please report this at https://github.com/ansible-collections/community.docker/issues/new?assignees=&labels=&projects=&template=bug_report.md
[WARNING]: Cannot parse event from line: 'f2543dc9f0a9 Downloading 25.36kB/2.425MB'. Please report this at https://github.com/ansible-collections/community.docker/issues/new?assignees=&labels=&projects=&template=bug_report.md
[WARNING]: Cannot parse event from line: '972e292d3a60 Downloading 5.925MB/10.43MB'. Please report this at https://github.com/ansible-collections/community.docker/issues/new?assignees=&labels=&projects=&template=bug_report.md
[WARNING]: Cannot parse event from line: 'f2543dc9f0a9 Downloading 2.219MB/2.425MB'. Please report this at https://github.com/ansible-collections/community.docker/issues/new?assignees=&labels=&projects=&template=bug_report.md
[WARNING]: Cannot parse event from line: 'f2543dc9f0a9 Extracting 32.77kB/2.425MB'. Please report this at https://github.com/ansible-collections/community.docker/issues/new?assignees=&labels=&projects=&template=bug_report.md
[WARNING]: Cannot parse event from line: '4f4fb700ef54 Downloading 32B/32B'. Please report this at https://github.com/ansible-collections/community.docker/issues/new?assignees=&labels=&projects=&template=bug_report.md
[WARNING]: Cannot parse event from line: 'f2543dc9f0a9 Extracting 2.425MB/2.425MB'. Please report this at https://github.com/ansible-collections/community.docker/issues/new?assignees=&labels=&projects=&template=bug_report.md
[WARNING]: Cannot parse event from line: '972e292d3a60 Extracting 131.1kB/10.43MB'. Please report this at https://github.com/ansible-collections/community.docker/issues/new?assignees=&labels=&projects=&template=bug_report.md
[WARNING]: Cannot parse event from line: '972e292d3a60 Extracting 10.43MB/10.43MB'. Please report this at https://github.com/ansible-collections/community.docker/issues/new?assignees=&labels=&projects=&template=bug_report.md
[WARNING]: Cannot parse event from line: '238022553356 Extracting 541B/541B'. Please report this at https://github.com/ansible-collections/community.docker/issues/new?assignees=&labels=&projects=&template=bug_report.md
[WARNING]: Cannot parse event from line: '4f4fb700ef54 Extracting 32B/32B'. Please report this at https://github.com/ansible-collections/community.docker/issues/new?assignees=&labels=&projects=&template=bug_report.md
The text was updated successfully, but these errors were encountered:
#786 should parse these messages correctly. Thanks for reporting this! I hope that eventually Docker Compose will have machine-readable output and we don't have to play this cat and mouse game anymore :)
SUMMARY
When using
community.docker.docker_compose_v2_pull
it prints warnings and asks to report an issue.Similar to #778, but probably a bit different.
ISSUE TYPE
COMPONENT NAME
community.docker.docker_compose_v2_pull
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
STEPS TO REPRODUCE
It feels like this happens on a new, not pulled yet images. After second run these warning are gone.
EXPECTED RESULTS
No warnings.
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: