From 354625d8c4db9ce94c4827cc1484e6b46998e965 Mon Sep 17 00:00:00 2001 From: Robert Field Date: Wed, 8 Apr 2026 15:04:00 +0100 Subject: [PATCH] fix: publish-hostless workflow picks wrong container image from ECS The workflow used containerDefinitions[0] to get the deployed WAB image, but index 0 is the Fluent Bit log-router sidecar, not the WAB container. This caused the publish-hostless Docker image to be built on top of the Fluent Bit image (which has no node binary), resulting in exit code 127: "node: command not found". Fix: query by container name 'wab' instead of array index. Verified by pulling both images locally: - WAB image: /usr/local/bin/node exists (125MB, v24.14.1) - publish-hostless image: node binary completely missing (built on Fluent Bit base instead of WAB base) --- .github/workflows/publish-hostless.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/publish-hostless.yml b/.github/workflows/publish-hostless.yml index be9227143..4320a5761 100644 --- a/.github/workflows/publish-hostless.yml +++ b/.github/workflows/publish-hostless.yml @@ -57,10 +57,10 @@ jobs: exit 1 fi - # Get image from task definition + # Get WAB container image (not the sidecar containers like log-router or datadog-agent) DEPLOYED_IMAGE=$(aws ecs describe-task-definition \ --task-definition "$TASK_DEF_ARN" \ - --query 'taskDefinition.containerDefinitions[0].image' \ + --query "taskDefinition.containerDefinitions[?name=='wab'].image | [0]" \ --output text) echo "::add-mask::$DEPLOYED_IMAGE"