ansible-collections/community.docker
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.docker.git synced 2026-07-29 11:55:04 +00:00
Code Packages Projects Releases Wiki Activity

Release 3.8.1.

Browse Source
This commit is contained in:
Felix Fontein
2024-03-16 20:16:57 +01:00
parent 61c54874fd
commit 59a8220c7f
8 changed files with 369 additions and 303 deletions
Download Patch File Download Diff File Expand all files Collapse all files
changelogs/changelog.yaml
+32
View File
@@ -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'