English · Java
Appearance
English · Java
Appearance
[Dockerfile.noble] can be used to run Playwright scripts in Docker environment. This image includes the Playwright browsers and browser system dependencies. The Playwright package/dependency is not included in the image and should be installed separately.
This Docker image is published to [Microsoft Artifact Registry].
INFO
This Docker image is intended to be used for testing and development purposes only. It is not recommended to use this Docker image to visit untrusted websites.
docker pull mcr.microsoft.com/playwright/java:v%%VERSION%%-nobleBy default, the Docker image will use the root user to run the browsers. This will disable the Chromium sandbox which is not available with root. If you run trusted code (e.g. End-to-end tests) and want to avoid the hassle of managing separate user then the root user may be fine. For web scraping or crawling, we recommend to create a separate user inside the Docker container and use the seccomp profile.
On trusted websites, you can avoid creating a separate user and use root for it since you trust the code which will run on the browsers.
docker run -it --rm --ipc=host mcr.microsoft.com/playwright/java:v%%VERSION%%-noble /bin/bashOn untrusted websites, it's recommended to use a separate user for launching the browsers in combination with the seccomp profile. Inside the container or if you are using the Docker image as a base image you have to use adduser for it.
docker run -it --rm --ipc=host --user pwuser --security-opt seccomp=seccomp_profile.json mcr.microsoft.com/playwright/java:v%%VERSION%%-noble /bin/bashseccomp_profile.json is needed to run Chromium with sandbox. This is a default Docker seccomp profile with extra user namespace cloning permissions:
{
"comment": "Allow create user namespaces",
"names": [
"clone",
"setns",
"unshare"
],
"action": "SCMP_ACT_ALLOW",
"args": [],
"includes": {},
"excludes": {}
}When running Playwright in Docker, the following configuration is recommended:
--init Docker flag is recommended to avoid special treatment for processes with PID=1. This is a common reason for zombie processes.--ipc=host is recommended when using Chromium. Without it, Chromium can run out of memory and crash. Learn more about this option in Docker docs.docker run --cap-add=SYS_ADMIN when developing locally.See our Continuous Integration guides for sample configs.
You can run Playwright Server in Docker while keeping your tests running on the host system or another machine. This is useful for running tests on unsupported Linux distributions or remote execution scenarios.
Start the Playwright Server in Docker:
docker run -p 3000:3000 --rm --init -it --workdir /home/pwuser --user pwuser mcr.microsoft.com/playwright:v%%VERSION%%-noble /bin/sh -c "npx -y playwright@%%VERSION%% run-server --port 3000 --host 0.0.0.0"WARNING
The Playwright Server has no authentication. Any client that can reach the port gets full control of the browsers and can act as the user that runs the server. The server is intended to run in an environment where the network configuration restricts access to the port. Publish the port only to trusted clients, for example with -p 127.0.0.1:3000:3000 when the tests run on the same machine, or with a firewall, a private network or an authenticating proxy otherwise.
If other local users or processes must not connect, for example on a shared development machine, serve the endpoint at an unguessable path with --path /<secret> and connect to ws://127.0.0.1:3000/<secret>.
package org.example;
import com.microsoft.playwright.*;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
try (Playwright playwright = Playwright.create()) {
Browser browser = playwright.chromium().connect("ws://127.0.0.1:3000/");
}
}
}If you need to access local servers from within the Docker container:
docker run --add-host=hostmachine:host-gateway -p 3000:3000 --rm --init -it --workdir /home/pwuser --user pwuser mcr.microsoft.com/playwright:v%%VERSION%%-noble /bin/sh -c "npx -y playwright@%%VERSION%% run-server --port 3000 --host 0.0.0.0"This makes hostmachine point to the host's localhost. Your tests should use hostmachine instead of localhost when accessing local servers.
INFO
When running tests remotely, ensure the Playwright version in your tests matches the version running in the Docker container.
For Docker and GitHub Codespaces environments, you can view and generate tests using the noVNC viewer built into the Docker image. In order for the VNC webviewer to be accessible outside of the container, you can enable the desktop-lite feature and specify the webPort in your .devcontainer/devcontainer.json file:
{
"image": "mcr.microsoft.com/playwright:v%%VERSION%%-noble",
"forwardPorts": [6080],
"features": {
"desktop-lite": {
"webPort": "6080"
}
}
}Once this is enabled you can open the port specified in a new browser tab and you will have access to the noVNC web viewer. This will enable you to record tests, pick selectors, and use codegen directly on your container.
See [all available image tags].
We currently publish images with the following tags:
:v%%VERSION%% - Playwright v%%VERSION%% release docker image based on Ubuntu 24.04 LTS (Noble Numbat).:v%%VERSION%%-noble - Playwright v%%VERSION%% release docker image based on Ubuntu 24.04 LTS (Noble Numbat).:v%%VERSION%%-jammy - Playwright v%%VERSION%% release docker image based on Ubuntu 22.04 LTS (Jammy Jellyfish).:v%%VERSION%%-resolute - Playwright v%%VERSION%% release docker image based on Ubuntu 26.04 LTS (Resolute Raccoon).INFO
It is recommended to always pin your Docker image to a specific version if possible. If the Playwright version in your Docker image does not match the version in your project/tests, Playwright will be unable to locate browser executables.
We currently publish images based on the following Ubuntu versions:
resolutenoblejammyBrowser builds for Firefox and WebKit are built for the glibc library. Alpine Linux and other distributions that are based on the musl standard library are not supported.