Skip to content

Commit

Permalink
Release 3.8.1.
Browse files Browse the repository at this point in the history
  • Loading branch information
felixfontein committed Mar 16, 2024
1 parent 61c5487 commit 59a8220
Show file tree
Hide file tree
Showing 8 changed files with 342 additions and 276 deletions.
552 changes: 289 additions & 263 deletions CHANGELOG.md

Large diffs are not rendered by default.

21 changes: 21 additions & 0 deletions CHANGELOG.rst
Expand Up @@ -4,6 +4,27 @@ Docker Community Collection Release Notes

.. contents:: Topics

v3.8.1
======

Release Summary
---------------

Bugfix release

Security Fixes
--------------

- docker_containers, docker_machine, and docker_swarm inventory plugins - make sure all data received from the Docker daemon / Docker machine is marked as unsafe, so remote code execution by obtaining texts that can be evaluated as templates is not possible (https://www.die-welt.net/2024/03/remote-code-execution-in-ansible-dynamic-inventory-plugins/, https://github.com/ansible-collections/community.docker/pull/815).

Bugfixes
--------

- docker_compose_v2 - do not fail when non-fatal errors occur. This can happen when pulling an image fails, but then the image can be built for another service. Docker Compose emits an error in that case, but ``docker compose up`` still completes successfully (https://github.com/ansible-collections/community.docker/issues/807, https://github.com/ansible-collections/community.docker/pull/810, https://github.com/ansible-collections/community.docker/pull/811).
- docker_compose_v2* modules - correctly parse ``Warning`` events emitted by Docker Compose (https://github.com/ansible-collections/community.docker/issues/807, https://github.com/ansible-collections/community.docker/pull/811).
- docker_compose_v2* modules - parse ``logfmt`` warnings emitted by Docker Compose (https://github.com/ansible-collections/community.docker/issues/787, https://github.com/ansible-collections/community.docker/pull/811).
- docker_compose_v2_pull - fixing idempotence by checking actual pull progress events instead of service-level pull request when ``policy=always``. This stops the module from reporting ``changed=true`` if no actual change happened when pulling. In check mode, it has to assume that a change happens though (https://github.com/ansible-collections/community.docker/issues/813, https://github.com/ansible-collections/community.docker/pull/814).

v3.8.0
======

Expand Down
32 changes: 32 additions & 0 deletions changelogs/changelog.yaml
Expand Up @@ -1591,3 +1591,35 @@ releases:
- 803-compose-v2-pull.yml
- 804-compose-v2-waiting.yml
release_date: '2024-02-25'
3.8.1:
changes:
bugfixes:
- docker_compose_v2 - do not fail when non-fatal errors occur. This can happen
when pulling an image fails, but then the image can be built for another service.
Docker Compose emits an error in that case, but ``docker compose up`` still
completes successfully (https://github.com/ansible-collections/community.docker/issues/807,
https://github.com/ansible-collections/community.docker/pull/810, https://github.com/ansible-collections/community.docker/pull/811).
- docker_compose_v2* modules - correctly parse ``Warning`` events emitted by
Docker Compose (https://github.com/ansible-collections/community.docker/issues/807,
https://github.com/ansible-collections/community.docker/pull/811).
- docker_compose_v2* modules - parse ``logfmt`` warnings emitted by Docker Compose
(https://github.com/ansible-collections/community.docker/issues/787, https://github.com/ansible-collections/community.docker/pull/811).
- docker_compose_v2_pull - fixing idempotence by checking actual pull progress
events instead of service-level pull request when ``policy=always``. This
stops the module from reporting ``changed=true`` if no actual change happened
when pulling. In check mode, it has to assume that a change happens though
(https://github.com/ansible-collections/community.docker/issues/813, https://github.com/ansible-collections/community.docker/pull/814).
release_summary: Bugfix release
security_fixes:
- docker_containers, docker_machine, and docker_swarm inventory plugins - make
sure all data received from the Docker daemon / Docker machine is marked as
unsafe, so remote code execution by obtaining texts that can be evaluated
as templates is not possible (https://www.die-welt.net/2024/03/remote-code-execution-in-ansible-dynamic-inventory-plugins/,
https://github.com/ansible-collections/community.docker/pull/815).
fragments:
- 3.8.1.yml
- 810-compose-errors.yml
- 811-compose-v2-logfmt.yml
- 814-docker_compose_v2_pull-idem.yml
- inventory-rce.yml
release_date: '2024-03-16'
1 change: 0 additions & 1 deletion changelogs/fragments/3.8.1.yml

This file was deleted.

5 changes: 0 additions & 5 deletions changelogs/fragments/810-compose-errors.yml

This file was deleted.

3 changes: 0 additions & 3 deletions changelogs/fragments/811-compose-v2-logfmt.yml

This file was deleted.

2 changes: 0 additions & 2 deletions changelogs/fragments/814-docker_compose_v2_pull-idem.yml

This file was deleted.

2 changes: 0 additions & 2 deletions changelogs/fragments/inventory-rce.yml

This file was deleted.

0 comments on commit 59a8220

Please sign in to comment.