github/puppeteer
0
0
Fork 0
mirror of https://github.com/puppeteer/puppeteer synced 2024-06-14 14:02:48 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(troubleshooting): add note on --disable-dev-shm-usage for Docker (#1603)

Browse Source
This commit is contained in:
Eric Bidelman 2018-01-04 13:52:13 -08:00 committed by Andrey Lushnikov
parent ed3fc47069
commit 32a7fd5f37
1 changed files with 12 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/troubleshooting.md
View File

@ -160,11 +160,19 @@ how to run this Dockerfile from a webserver running on App Engine Flex (Node).
By default, Docker runs a container with a `/dev/shm` shared memory space 64MB. By default, Docker runs a container with a `/dev/shm` shared memory space 64MB.
This is [typically too small](https://github.com/c0b/chrome-in-docker/issues/1) for Chrome This is [typically too small](https://github.com/c0b/chrome-in-docker/issues/1) for Chrome
and will cause Chrome to crash when rendering large pages. To fix, run the container and will cause Chrome to crash when rendering large pages. To fix, run the container with
with `docker run --shm-size=1gb` to increase the size of `/dev/shm`. In the future, `docker run --shm-size=1gb` to increase the size of `/dev/shm`. Since Chrome 65, this is no
this won't be necessary. See [crbug.com/736452](https://bugs.chromium.org/p/chromium/issues/detail?id=736452). longer necessary. Instead, launch the browser with the `--disable-dev-shm-usage` flag:
If you're seeing other weird errors when launching Chrome, try running the container ```js
const browser = await puppeteer.launch({
args: ['--disable-dev-shm-usage']
});
```
This will write shared memory files into `/tmp` instead of `/dev/shm`. See [crbug.com/736452](https://bugs.chromium.org/p/chromium/issues/detail?id=736452) for more details.
Seeing other weird errors when launching Chrome? Try running your container
with `docker run --cap-add=SYS_ADMIN` when developing locally. Since the Dockerfile with `docker run --cap-add=SYS_ADMIN` when developing locally. Since the Dockerfile
adds a `pptr` user as a non-privileged user, it may not have all the necessary privileges. adds a `pptr` user as a non-privileged user, it may not have all the necessary privileges.