packaged by Chainguard
Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.
Playwright web testing and automation framework with the Chromium browser only.
Chainguard Containers are regularly-updated, secure-by-default container images.
For those with access, this container image is available on cgr.dev:
Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.
This image supports Chromium only. It provides the Playwright CLI (built with TypeScript on Node.js, tracking upstream v1.63.0) together with Chainguard's Chromium. It is intended as a drop-in replacement for mcr.microsoft.com/playwright for projects that test with Chromium. Tests that launch Firefox or WebKit (firefox.launch(), webkit.launch(), or Playwright projects that use them) fail in this image, and playwright install firefox or playwright install webkit downloads upstream builds that are not supported here.
The image matches upstream's runtime configuration: no entrypoint, a default command of /bin/bash, PLAYWRIGHT_BROWSERS_PATH=/ms-playwright, and Node.js 24 with npm, npx, yarn, corepack, git, and ssh. Like upstream, it runs as root and includes a pwuser user (UID 1001) for docker run --user pwuser. It also includes the fonts upstream installs (Liberation, FreeFont, Noto Color Emoji, IPA Gothic, WenQuanYi Zen Hei, and Loma) with a fontconfig setup (FONTCONFIG_FILE) that resolves them as upstream does, so pages render with the same fonts. One exception: in headless mode, upstream's separate headless shell renders Japanese with WenQuanYi Zen Hei, while this image renders it with IPA P Gothic, as upstream's full Chromium does. Projects that depend on @playwright/test at the matching version run with npx playwright test as they do upstream. The Playwright CLI is also installed globally as playwright.
Key differences from the upstream image:
playwright install. It is registered in /ms-playwright as a completed Playwright install of the matching revision, so the CLI and chromium.launch() work without executablePath, and playwright install chromium is a no-op.playwright install --with-deps is not supported, because it installs system packages with apt-get. The dependencies are already present, so run playwright install without --with-deps or skip it.recordVideo) uses a Chainguard ffmpeg build with libvpx, registered where Playwright expects its own ffmpeg build.Xvfb and xvfb-run are included for headed browsers. xvfb-run hangs if it runs as PID 1, so pass --init to docker run when using it as the container command, as upstream recommends.Check the installed Playwright version:
Run a Playwright script from your project by mounting it into the container:
To run a Playwright Test project, install its dependencies and run it in the container:
The image sets the following environment variables:
LANG=C.UTF-8LC_ALL=C.UTF-8PLAYWRIGHT_BROWSERS_PATH=/ms-playwrightFONTCONFIG_FILE=/usr/share/playwright/fontconfig/fonts.confPlaywright is licensed under the Apache License 2.0.
Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.
All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.
The main features of Chainguard Containers include:
For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.
In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.
Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.
To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.
To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.
Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.
This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.
Chainguard's container images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" tag of this image:
AFL-2.1
Apache-2.0
BSD-1-Clause
BSD-2-Clause
BSD-3-Clause
BSD-4-Clause
BSD-4-Clause-UC
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreementChainguard Containers are SLSA Level 3 compliant with detailed metadata and documentation about how it was built. We generate build provenance and a Software Bill of Materials (SBOM) for each release, with complete visibility into the software supply chain.
SLSA compliance at ChainguardThis image helps reduce time and effort in establishing PCI DSS 4.0 compliance with low-to-no CVEs.
PCI DSS at Chainguard