From 805c75685531dc5b3319b54ba6362bdf92863ee4 Mon Sep 17 00:00:00 2001
From: Ognyan Genev <39865181+ogenev@users.noreply.github.com>
Date: Mon, 7 Oct 2024 12:18:01 +0300
Subject: [PATCH] chore(book): add a note about resolving `docker_compose_v2`
 error in ansible (#1502)

---
 book/src/developers/contributing/releases/deployment.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/book/src/developers/contributing/releases/deployment.md b/book/src/developers/contributing/releases/deployment.md
index 04abfdd3d..85aca014f 100644
--- a/book/src/developers/contributing/releases/deployment.md
+++ b/book/src/developers/contributing/releases/deployment.md
@@ -64,6 +64,8 @@ This step directs Ansible to use the current master version of trin. Read [about
 - Run Glados deployment: updates glados + portal client (currently configured as trin, but this could change)
     - `cd ../../glados/ansible`
     - `ansible-playbook playbook.yml --tags glados`
+- if you experience "couldn't resolve module/action 'community.docker.docker_compose_v2'" error, you might need to re-install the community.docker collection:
+    - `ansible-galaxy collection install community.docker --force`
 - Wait for completion
 - Launch a fresh trin node, check it against the bootnodes
 - ssh into random nodes, one of each kind, to check the logs: