Skip to content
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

[stable-3] docker_image_build: add note on strange behavior #1007

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions changelogs/fragments/1007-build-output.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
known_issues:
- "docker_image_build - when ``outputs`` is specified, all entries with ``type=image``, ``type=oci`` and ``type=docker`` have their
name overwritten by the values provided in ``name`` and ``tag``. This happens because the module provides the ``--tag`` option
with the values of the ``name`` and ``tag`` options to Docker the buildx plugin, which for some reason takes that value and
uses it to overwrite the values in ``--output`` parameters
(https://github.com/ansible-collections/community.docker/issues/1001, https://github.com/ansible-collections/community.docker/pull/1007)."
4 changes: 4 additions & 0 deletions plugins/modules/docker_image_build.py
Original file line number Diff line number Diff line change
Expand Up @@ -175,6 +175,10 @@
be created, which can cause the basic idempotency this module offers to not work.
- Providing an empty list to this option is equivalent to not specifying it at all.
The default behavior is a single entry with O(outputs[].type=image).
- B(Note) that for some reason Docker the buildx plugin overwrites the image name
of every entry with O(outputs[].type=image), O(outputs[].type=oci), or O(outputs[].type=docker)
with the image name specified in O(name)/O(tag). We will not work around this in community.docker 3.x.y
for backwards compatibility. Please upgrade to community.docker 4.2.0 or newer for a workaround.
type: list
elements: dict
version_added: 3.10.0
Expand Down
Loading