From 07a0021dcaa5389a96283389392c3d01d63c0d6a Mon Sep 17 00:00:00 2001
From: yh-noh <yhnoh@mz.co.kr>
Date: Tue, 29 Sep 2026 00:21:13 +0000
Subject: [PATCH] fix(cost): add restart policy to mc-cost-optimizer-db

mc-cost-optimizer-db had no restart policy (default: no), so it was not
brought back after a host reboot while the dependent cost services
(restart: on-failure) kept crash-looping on UnknownHostException.
Align with other DB services in the file by using restart: always.
---
 conf/docker/docker-compose.yaml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/conf/docker/docker-compose.yaml b/conf/docker/docker-compose.yaml
index 7930caa..8bfbb28 100644
--- a/conf/docker/docker-compose.yaml
+++ b/conf/docker/docker-compose.yaml
@@ -890,6 +890,7 @@ services:
   mc-cost-optimizer-db:
     image: mariadb:12.3.2
     container_name: mc-cost-optimizer-db
+    restart: always
     depends_on:
       mc-cost-optimizer-init-volume:
         condition: service_completed_successfully