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.
This commit is contained in:
Miguel Ángel
2026-10-22 12:18:18 -04:00
parent 7474f38420
commit 3366845def
+4 -1
View File
@@ -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