From c97f1f73ce1be800b04c039a9fd4dcb94154222a Mon Sep 17 00:00:00 2001 From: Jerod Hodgkin Date: Mon, 20 Jul 2026 05:30:06 +0000 Subject: [PATCH] Prune old image generations after each prod deploy Each promotion pulls a uniquely SHA-tagged image, so without cleanup old generations accumulate indefinitely. CT111's disk is small (was 5.9GB, just grown to 8.8GB) and filled up mid-pull on the first real promotion attempt. Prune dangling images after up -d swaps traffic to the new containers, once their predecessors are no longer referenced. --- .gitea/workflows/deploy-prod.yml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.gitea/workflows/deploy-prod.yml b/.gitea/workflows/deploy-prod.yml index 5dd4bee..6c39f08 100644 --- a/.gitea/workflows/deploy-prod.yml +++ b/.gitea/workflows/deploy-prod.yml @@ -44,7 +44,9 @@ jobs: export IMAGE_TAG=$SHA docker compose -f docker-compose.yml -f docker-compose.deploy.yml pull docker compose -f docker-compose.yml -f docker-compose.deploy.yml up -d - echo "Deployed $SHA (pulled, not built)"' + echo "Deployed $SHA (pulled, not built)" + docker image prune -af + echo "Pruned old image generations"' - name: Wait for health check run: |