mirror of
https://github.com/puppeteer/puppeteer
synced 2024-06-14 14:02:48 +00:00
990635abc9
🤖 I have created a release *beep* *boop* --- <details><summary>puppeteer: 19.2.1</summary> ### Dependencies * The following workspace dependencies were updated * dependencies * puppeteer-core bumped from 19.2.0 to ^19.2.1 </details> <details><summary>puppeteer-core: 19.2.1</summary> ## [19.2.1](https://github.com/puppeteer/puppeteer/compare/puppeteer-core-v19.2.0...puppeteer-core-v19.2.1) (2022-10-28) ### Bug Fixes * resolve navigation requests when request fails ([#9178](https://github.com/puppeteer/puppeteer/issues/9178)) ([c11297b
](c11297baa5
)), closes [#9175](https://github.com/puppeteer/puppeteer/issues/9175) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
1.2 KiB
1.2 KiB
Docker
Puppeteer offers a Docker image that includes Chromium along with the required
dependencies and a pre-installed Puppeteer version. The image is available via
the
GitHub Container Registry.
The latest image is tagged as latest
and other tags match Puppeteer versions.
For example,
docker pull ghcr.io/puppeteer/puppeteer:latest # pulls the latest
docker pull ghcr.io/puppeteer/puppeteer:16.1.0 # pulls the image that contains Puppeteer v16.1.0
The image is meant for running the browser in sandbox mode and therefore,
running the image requires the SYS_ADMIN
capability.
Usage
To use the docker image directly, run:
docker run -i --init --cap-add=SYS_ADMIN --rm ghcr.io/puppeteer/puppeteer:latest node -e "$(cat path/to/script.js)"
where path/to/script.js
is the path relative to your working directory. Note
the image requires the SYS_ADMIN
capability since the browser runs in sandbox
mode.
If you need to build an image based on a different base image, you can use our
Dockerfile
as the starting point.