From 2e539ed330d406d36dea704caffeac45decdf415 Mon Sep 17 00:00:00 2001 From: Michael Schiemer Date: Tue, 4 Nov 2025 15:32:36 +0100 Subject: [PATCH] fix(deployment): explicitly override build sections with null in production Added 'build: null' to web, php, and queue-worker services in docker-compose.production.yml to explicitly remove build sections inherited from base config. This fixes 'lstat /home/deploy/deployment/stacks/application/docker/php: no such file or directory' error during deployment, as production servers only have docker-compose files, not build context. Registry-based deployment should pull pre-built images, not attempt to build on production server. --- docker-compose.production.yml | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docker-compose.production.yml b/docker-compose.production.yml index 957e7acc..ca538b63 100644 --- a/docker-compose.production.yml +++ b/docker-compose.production.yml @@ -12,8 +12,9 @@ services: web: - # Use pre-built image from registry + # Use pre-built image from registry (override build from base) image: git.michaelschiemer.de:5000/framework:latest + build: null # Explicitly remove build section from base # Production restart policy restart: always @@ -78,8 +79,9 @@ services: condition: service_started php: - # Use pre-built image from registry + # Use pre-built image from registry (override build from base) image: git.michaelschiemer.de:5000/framework:latest + build: null # Explicitly remove build section from base # Production restart policy restart: always @@ -227,8 +229,9 @@ services: labels: "service,environment" queue-worker: - # Use pre-built image from registry + # Use pre-built image from registry (override build from base) image: git.michaelschiemer.de:5000/framework:latest + build: null # Explicitly remove build section from base # Production restart policy restart: always