Playwright · infra · fg-0316

Executable doesn't exist at /ms-playwright/chromium-XXXX inside the official Playwright Docker image

browserType.launch: Executable doesn't exist at /ms-playwright/chromium_headless_shell-1208/chrome-headless-shell-linux64/chrome-headless-shell

Verified 2026-10-15 · Confirmed by 0 builders · Trust 50/100

Cause

Each Playwright release expects one exact browser build number, and the image only ships the builds for its own tag. A caret range in package.json or a floating image tag lets the npm package and the image drift apart.

Fix

Pin @playwright/test to an exact version and use the image tag with the same version. Upgrade both in one commit.

Apply

# package.json: "@playwright/test": "1.64.0"  (no caret)
FROM mcr.microsoft.com/playwright:v1.64.0-noble

Affects: All Playwright versions using mcr.microsoft.com/playwright images; browser build numbers change with most minor releases

Sources

• https://playwright.dev/docs/docker
• https://github.com/microsoft/playwright/issues/39122

claude mcp add --transport http footgun https://getfootgun.com/api/mcp