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.adduser
for it.seccomp_profile.json
is needed to run Chromium with sandbox. This is a default Docker seccomp profile with extra user namespace cloning permissions:--ipc=host
is recommended when using Chrome (Docker docs). Chrome can run out of memory without this flag.//utils/docker/build.sh
to build the image.playwright:localbuild-bionic
and could be run as: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).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).