Felix Fontein

The module passes that information on to the Docker daemon. If you get an error, then that's because the Docker daemon doesn't handle it as you expect. Also you might...

A big problem seems to be that it is impossible to figure out from the output whether the image is actually built (the actions always say "Built" and that's it,...

I created https://github.com/docker/compose/issues/13040 for the latter. While looking at that, I also noticed that `docker compose up --dry-run` also builds the images. This is also a problem for the docker_compose_v2...

The Compose issue has been closed with https://github.com/docker/compose/pull/13042. Once that's released, build will simply output some generic messages which basically always say "build happened" (whether the images were actually updated...

BTW, @fgruenbauer you might be interested in https://forum.ansible.com/t/keycloak-modules-in-community-general/41746.

@fgruenbauer how do you want to proceed with this PR?

Ping @fgruenbauer needs_info

Kind of related ot #651. Having that right now would force us to use classifiers that were just supported by setuptools since last week, which sounds dangerous to me.

I guess the problem is in line 404 (https://github.com/ansible-collections/community.general/blob/main/plugins/callback/elastic.py#L404), where `included_file` is passed in to `finish_task()`'s `result` parameter.

No idea, sorry. Maybe @v1v can help here?