From 3366845defd976575bf0b764df0fa89fa1bf99db Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Miguel=20=C3=81ngel?= Date: Thu, 22 Oct 2026 11:36:00 -0400 Subject: [PATCH] fix(aws-lambda): launch Chrome in the image smoke the way Lambda does @sparticuz/chromium inflates its AL2023 libraries only when AWS_EXECUTION_ENV names a Node runtime; Lambda sets it, a bare docker run does not. The workflow also runs on @sparticuz/chromium bumps and handler ZIP layout changes, which re-stage the image. --- .github/workflows/lambda-arm64-image.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.github/workflows/lambda-arm64-image.yml b/.github/workflows/lambda-arm64-image.yml index 0a1338d4f2..f66129a21c 100644 --- a/.github/workflows/lambda-arm64-image.yml +++ b/.github/workflows/lambda-arm64-image.yml @@ -10,6 +10,9 @@ on: paths: - "packages/aws-lambda/image/**" - "packages/aws-lambda/scripts/stage-arm64-image.ts" + # A @sparticuz/chromium bump or a ZIP layout change must re-stage the image. + - "packages/aws-lambda/package.json" + - "packages/aws-lambda/scripts/build-zip.ts" - ".github/workflows/lambda-arm64-image.yml" workflow_dispatch: @@ -85,7 +88,7 @@ jobs: --build-context task=staged/task --load -t hf-video:ci packages/aws-lambda/image - name: ffmpeg and Chrome run in the image run: >- - docker run --rm --entrypoint /var/lang/bin/node + docker run --rm --entrypoint /var/lang/bin/node -e AWS_EXECUTION_ENV=AWS_Lambda_nodejs22.x -v "$PWD/packages/aws-lambda/image/smoke-video.mjs:/var/task/smoke-video.mjs:ro" hf-video:ci /var/task/smoke-video.mjs - name: The Lambda runtime loads the handler