From 373f393b035c0e18a4ab7f1e16ecc26677954335 Mon Sep 17 00:00:00 2001
From: amir-climy <amirrudin.yahaya@gmail.com>
Date: Tue, 19 May 2026 19:50:53 +0800
Subject: [PATCH] fix(install): pull latest image before starting containers

Without an explicit pull, compose up reuses the locally cached image even
when a newer one is available on the registry. This caused the old image
(without --chmod=755) to be used on re-runs. Pull first to guarantee the
current released image is always used.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 manage-server/install.sh | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/manage-server/install.sh b/manage-server/install.sh
index 2609dca..eeef43b 100755
--- a/manage-server/install.sh
+++ b/manage-server/install.sh
@@ -87,6 +87,10 @@ else
     info "reusing existing .env at $ENV_FILE"
 fi
 
+# ── pull latest image ────────────────────────────────────────────────────
+info "pulling latest image..."
+"${COMPOSE[@]}" --env-file "$ENV_FILE" pull manage-server
+
 # ── start ────────────────────────────────────────────────────────────────
 info "starting containers..."
 "${COMPOSE[@]}" --env-file "$ENV_FILE" up -d