Dockerfile.bionic and Dockerfile.focal can be used to run Playwright scripts in Docker environments. These images includes all the dependencies needed to run browsers in a Docker container, including browsers.
- Image tags
- Base images
This image is published on Docker Hub.
By 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.
On 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.
--ipc=hostis recommended when using Chrome (Docker docs). Chrome can run out of memory without this flag.
See our Continuous Integration guides for sample configs.
//docs/docker/build.sh to build the image.
The image will be tagged as
playwright:localbuild-bionic and could be run as:
Docker images are published automatically by GitHub Actions. We currently publish the following images:
mcr.microsoft.com/playwright:next- tip-of-tree image version.
mcr.microsoft.com/playwright:bionic- last Playwright release docker image.
mcr.microsoft.com/playwright:sha-XXXXXXX- docker image for every commit that changed docker files or browsers, marked with a short sha (first 7 digits of the SHA commit).
Status of push to MCR can be verified here (internal link).
mcr.microsoft.com/playwright:focal is based on Ubuntu 20.04 LTS (Focal Fossa).
mcr.microsoft.com/playwright:bionic is based on Ubuntu 18.04 LTS (Bionic Beaver).