primatekuntech/triton-install
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix(install): pull latest image before starting containers

Browse source 
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>
This commit is contained in:
amir-climy 2026-05-19 19:50:53 +08:00
parent 504242308c
commit 373f393b03
1 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
manage-server/install.sh
View file

@ -87,6 +87,10 @@ else
info "reusing existing .env at $ENV_FILE" info "reusing existing .env at $ENV_FILE"
fi fi
# ── pull latest image ────────────────────────────────────────────────────
info "pulling latest image..."
"${COMPOSE[@]}" --env-file "$ENV_FILE" pull manage-server
# ── start ──────────────────────────────────────────────────────────────── # ── start ────────────────────────────────────────────────────────────────
info "starting containers..." info "starting containers..."
"${COMPOSE[@]}" --env-file "$ENV_FILE" up -d "${COMPOSE[@]}" --env-file "$ENV_FILE" up -d