mcr.microsoft.com/playwright:v1.50.0-jammy, decoded

It is Microsoft's official Docker image for Playwright version 1.50.0, built on Ubuntu 22.04 LTS (the Jammy Jellyfish release, which is what the -jammy suffix means). It ships Node.js 22 and all three Playwright browser engines (Chromium, Firefox, and WebKit) preinstalled into /ms-playwright along with their Linux system dependencies. The tag is published on the Microsoft Container Registry, not Docker Hub, so you pull it from mcr.microsoft.com directly. As of 2026-06-19 the tag is still present on the registry alongside architecture-specific variants v1.50.0-jammy-amd64 and v1.50.0-jammy-arm64.

Both are Ubuntu base images. -jammy is Ubuntu 22.04 LTS and -noble is Ubuntu 24.04 LTS. For Playwright 1.50.0 the plain tag v1.50.0 resolves to the same default base the Playwright team chose for that release; the -jammy and -noble suffixes let you pin the exact Ubuntu version regardless of which one becomes the default later. If your CI runner or your app's runtime libraries expect glibc and system packages from 22.04, choose -jammy. If you need 24.04, choose -noble. The Playwright version inside both is identical (1.50.0); only the OS layer differs.

That error means the Playwright version in your project does not match the browsers baked into the image. The image installs browsers for exactly Playwright 1.50.0 into /ms-playwright, and the path includes a build number tied to that version (for example /ms-playwright/chromium-XXXX/chrome-linux/chrome). When your package.json pulls @playwright/test 1.52 or 1.55, the test runner looks for a different build number that was never downloaded, and launch fails. The official docs state it plainly: if the Playwright version in your Docker image does not match the version in your project, Playwright will be unable to locate browser executables. Fix it by setting @playwright/test to 1.50.x, or by switching to the image tag that matches the version you already use.

No. Playwright 1.50.0 was published on 2025-01-23 and was superseded by 1.50.1 on 2025-01-31, eight days later. The image tag v1.50.1-jammy exists on the registry. If you are pinning to the 1.50 line and want the bug fixes from the patch, pin to v1.50.1-jammy and set @playwright/test to 1.50.1 so the versions still match. v1.50.0-jammy remains useful when you need a byte-for-byte reproducible build of the original release.

Yes, with no special handling, because the test files are standard @playwright/test specs. Assrt generates real Playwright code, not a proprietary YAML or a closed runtime, so a generated tests/checkout.spec.ts runs under npx playwright test inside mcr.microsoft.com/playwright:v1.50.0-jammy exactly like a hand-written spec. The only requirement is the same version-match rule that applies to every Playwright project: your package.json @playwright/test must be on the 1.50.x line to match the browsers in the image.

No, and you should not. The browsers are already present at /ms-playwright and PLAYWRIGHT_BROWSERS_PATH is set to that path inside the image. Running npx playwright install again would download a second copy, bloat your layer, and possibly fetch a build number that does not match the system dependencies the image installed. Just run npx playwright test. The whole point of the official image is that the browser install step is already done and cached.

Yes. The registry publishes v1.50.0-jammy-amd64 and v1.50.0-jammy-arm64, and the multi-arch v1.50.0-jammy manifest resolves to the right one for your platform automatically. That means the same tag works on an Intel GitHub Actions runner and on an arm64 runner or an M-series laptop, and Docker pulls the matching architecture without you specifying it.

By default the container processes run as root, and the browser directory at /ms-playwright is created with 777 permissions so that any user you switch to can still read the browser binaries. If your CI requires a non-root user, you can add a USER directive in a derived Dockerfile; the 777 permission on /ms-playwright is specifically there so that a non-root user can still launch the browsers.