From 26b35467eca806fd44a7b16db0d2453e02ef227a Mon Sep 17 00:00:00 2001
From: yohan <783b8c87@scimetis.net>
Date: Fri, 1 Nov 2024 12:43:20 +0100
Subject: [PATCH] Reload reverse-proxy configuration when registry container
 has been restarted instead of restarting the whole container.

---
 roles/role_deploy_registry/tasks/main.yml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/roles/role_deploy_registry/tasks/main.yml b/roles/role_deploy_registry/tasks/main.yml
index 9a72f0c..fed72af 100644
--- a/roles/role_deploy_registry/tasks/main.yml
+++ b/roles/role_deploy_registry/tasks/main.yml
@@ -135,10 +135,10 @@
 
 # Workaround to prevent unexplained 503 error from reverse-proxy
 # after registry container restart
-- name: Restart reverse-proxy container service
-  ansible.builtin.systemd:
-    name: container-reverse-proxy
-    state: restarted
+- name: Reload reverse-proxy configuration
+  containers.podman.podman_container_exec:
+    name: reverse-proxy
+    command: 'sh -c ''service apache2 reload'''
   become: true
 
 - name: Add cloud.{{ DOMAIN }} to /etc/hosts