-
Notifications
You must be signed in to change notification settings - Fork 126
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
Cannot parse event from line: 'build service php' [docker_compose_v2] #778
Comments
It's just a warning. the module works properly. The information could be parsed and added to the actions: actions:
- id: matomo-php
status: build
what: image
- id: matomo_php_1
status: Recreate
what: container |
Which version of Docker Compose are you using? |
Hmm I was pretty sure that I already added code to handle these output messages, but apparently I didn't. |
Interestingly I only get these errors in dry-run mode, not with a regular run. I guess I have to add some more special cases then... 🤷 (Still wishing for docker/compose#10872...) |
Something else: there is only any indication that the image is built in dry-run mode. In regular mode, there's no indication that the image built happened (except that you see a build log in stdout, but parsing these... an even worse idea). |
I filed docker/compose#11403 for the missing non-dry-run indication that the image got built. |
SUMMARY
docker_compose_v2 unparsed output when compose decides that it needs to (re)build an image.
output of manual execution:
The
docker-compose.yml
has a service with build: configurationContext: the service is already running, started with legacy docker-compose, now docker compose wants to rebuild and recreate.
Additional note: @felixfontein It would be helpful for debugging, if the exact command the docker_compose_v2 module executes, is printed in the debug output.
ISSUE TYPE
COMPONENT NAME
docker_compose_v2
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: