Hi, it is safe to remove links directive

https://docs.docker.com/compose/compose-file/compose-file-v2/#links

ps. Thank you for your work!

Hi,

Could you please remove wait-for-it.sh script from Dockerfile and instead

1. add it in to repository and mount it inside the container before tests
2. Or download it inside command before tests

https://github.com/buildkite/docker-puppeteer/blob/master/example/docker-compose.integration-tests.yml#L10

It does not look good when something is downloaded from random place. And in this case it is only needed in tests.

Br,
Markku

Would it be possible to build several major versions for Node? 12/13/14?

It looks like 14 is the latest right now. I was wondering if in the future we can have something like buildkite/puppeteer:8/node:14?

[webmaster@localhost docker-puppeteer]$ docker-compose -f docker-compose.integration-tests.yml build --pull
app uses an image, skipping
Building tests
Step 1/3 : FROM buildkite/puppeteer:latest
Trying to pull repository docker.io/buildkite/puppeteer ...
sha256:e5b161ca16d91782549b58976cfe6ebebaaa76f76a2b1c92680f91ce0e7542a0: Pulling from docker.io/buildkite/puppeteer
Digest: sha256:e5b161ca16d91782549b58976cfe6ebebaaa76f76a2b1c92680f91ce0e7542a0
Status: Image is up to date for docker.io/buildkite/puppeteer:latest
---> d8855571c3f2
Step 2/3 : RUN npm i mocha
---> Using cache
---> 3fe3dd0e414b
Step 3/3 : ENV PATH "${PATH}:/node_modules/.bin"
---> Using cache
---> 208126a81ee6
Successfully built 208126a81ee6
[webmaster@localhost docker-puppeteer]$ docker-compose -f docker-compose.integration-tests.yml run tests
Creating docker-puppeteer_app_1 ... done

Started HeadlessChrome/72.0.3617.0
App
1) renders

0 passing (331ms)
1 failing

1. App
   renders:
   Error: net::ERR_CONNECTION_REFUSED at http://app/
   at navigate (/node_modules/puppeteer/lib/FrameManager.js:107:37)
   at process._tickCallback (internal/process/next_tick.js:68:7)
   -- ASYNC --
   at Frame. (/node_modules/puppeteer/lib/helper.js:144:27)
   at Page.goto (/node_modules/puppeteer/lib/Page.js:624:49)
   at Page. (/node_modules/puppeteer/lib/helper.js:145:23)
   at Context.it (/integration-tests/index.test.js:37:33)

But when I use curl http://app/ in tests container, I have web page content from app container

I m getting following error

Cannot start Chrome
[1030/100728.942574:ERROR:nacl_helper_linux.cc(310)] NaCl helper process running without a sandbox!
Most likely you need to configure your SUID sandbox correctly

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Preset name not found within published preset config (monorepo:babel6). Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

Why you are installing chrome and having all these installation statements in docker file, while you can use chromium from puppeteer itself?

Can you build a docker image with the current develop and push it to docker hub please.

same as title.

Hello,

I am Trying to run your Docker Container (Or Anything other with Chrome) on my Raspberry PI

Its installing just fine:

Sending build context to Docker daemon  4.608kB
Step 1/2 : FROM buildkite/puppeteer
 ---> 23a2e145eb22
Step 2/2 : CMD cd /app && node app.js
 ---> Running in ede1a47f24c0
Removing intermediate container ede1a47f24c0
 ---> 86d4fc5b2f41
Successfully built 86d4fc5b2f41
Successfully tagged node_puppeteer:latest

But on start with:
docker run -it --name my_name-v ~/projects/my_app/:/app node_puppeteer bash

standard_init_linux.go:211: exec user process caused "exec format error"

Do you have any Idea how i could get it running?

Hello,
After building with this image I found out that I was around 1.5 GB, I found out that it has a puppeteer v3 installed on it, so I removed the puppeteer v2 from my package.json but now I get that puppeteer is not installed.

Any idea on how to make it work with the included version?

thanks

Latest version in github is v1.13.0 but on Docker hub it's v1.11.0 ?

Can it be that Docker Hub doesn't automatically builds images for newest tags.

Hello!
Is tag v3.3.0 missing?

FROM buildkite/puppeteer:v3.3.0
manifest for buildkite/puppeteer:v3.3.0 not found: manifest unknow

I keep getting this error when I load my code:

UnhandledPromiseRejectionWarning: Error: Failed to launch chrome! spawn /app/node_modules/puppeteer/.local-chromium/linux-624487 ENOENT

Any thoughts on using Node.js v12 in your Dockerfile? It comes with a bunch of performance enhancements + new features

https://nodejs.org/en/about/releases/

What am I missing? What do I do wrong? What is it that I do not understand?

First session:

docker@boot2docker:/mnt/sdd1/tmp$ git clone https://github.com/buildkite/docker-puppeteer.git
Cloning into 'docker-puppeteer'...
remote: Enumerating objects: 408, done.
remote: Total 408 (delta 0), reused 0 (delta 0), pack-reused 408
Receiving objects: 100% (408/408), 131.98 KiB | 707.00 KiB/s, done.
Resolving deltas: 100% (193/193), done.
docker@boot2docker:/mnt/sdd1/tmp$ cd docker-puppeteer/example
docker@boot2docker:/mnt/sdd1/tmp/docker-puppeteer/example$
docker@boot2docker:/mnt/sdd1/tmp/docker-puppeteer/example$ # Build and run the example tests
docker@boot2docker:/mnt/sdd1/tmp/docker-puppeteer/example$ docker-compose -f docker-compose.integration-tests.yml run tests
WARNING: The Docker Engine you're using is running in swarm mode.

Compose does not use swarm mode to deploy services to multiple nodes in a swarm. All containers will be scheduled on the current node.

To deploy your application across the swarm, use `docker stack deploy`.

Creating example_web_1 ... done
wait-for-it.sh: waiting 15 seconds for web:80
wait-for-it.sh: web:80 is available after 0 seconds


  1) "before all" hook in "{root}"
  2) "after all" hook in "{root}"

  0 passing (2s)
  2 failing

  1) "before all" hook in "{root}":
     Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.


  2) "after all" hook in "{root}":
     TypeError: Cannot read property 'close' of undefined
      at Context.after (/integration-tests/index.test.js:32:17)



Started HeadlessChrome/75.0.3765.0

Second session;

docker@boot2docker:/mnt/sdd1/tmp$ ls -la /mnt/sdd1/tmp/docker-puppeteer/example/screenshots
total 8
drwxr-xr-x    2 root     root          4096 Nov 15 09:38 .
drwxr-xr-x    4 docker   staff         4096 Nov 15 09:38 ..

I found this while using this image in GitLab's CI environment, using jest-puppeteer. The default globalTeardown relies on the ps utility which is not included by default.

It errors out:

PASS functional-tests/app.test.js
Test Suites: 2 passed, 2 total
Tests:       5 passed, 5 total
Snapshots:   0 total
Time:        18.289 s
Ran all test suites.
events.js:292
      throw er; // Unhandled 'error' event
      ^
Error: spawn ps ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)
    at onErrorNT (internal/child_process.js:469:16)
    at processTicksAndRejections (internal/process/task_queues.js:84:21)
Emitted 'error' event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (internal/child_process.js:273:12)
    at onErrorNT (internal/child_process.js:469:16)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  errno: 'ENOENT',
  code: 'ENOENT',
  syscall: 'spawn ps',
  path: 'ps',
  spawnargs: [ '-o', 'pid', '--no-headers', '--ppid', 119 ]
}

Currently, I need to install the procps package after pulling the image (using before_script):

apt-get update && apt-get install -y procps

I suggest adding this to the base image instead.

Hi,

i'm on Windows 7 and tried the example tutorial as given.

But mocha seems unable to find test file:

`Building tests
Step 1/3 : FROM buildkite/puppeteer:latest
---> 17a11dfe4943
Step 2/3 : RUN npm i mocha
---> Running in 2d10174b7416
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.1 (node_modules/ch
okidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@
2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}
)
npm WARN !invalid#1 No description
npm WARN !invalid#1 No repository field.
npm WARN !invalid#1 No license field.

• [email protected]
  added 98 packages from 59 contributors and audited 289 packages in 8.355s

18 packages are looking for funding
run npm fund for details

found 0 vulnerabilities

Removing intermediate container 2d10174b7416
---> 27d86773687f
Step 3/3 : ENV PATH="${PATH}:/node_modules/.bin"
---> Running in 1fa249f3af22
Removing intermediate container 1fa249f3af22
---> 98a8b22ecb51
Successfully built 98a8b22ecb51
Successfully tagged example_tests:latest
WARNING: Image for service tests was built because it did not already exist. To
rebuild this image you must use docker-compose build or docker-compose up --b uild.
wait-for-it.sh: waiting 15 seconds for web:80
wait-for-it.sh: web:80 is available after 0 seconds
Error: No test files found`

I'm not a mocha expert but I would like to amend and use this project which seems very promising.

Can anybody help me?

thanks

Thank you for this Docker image, I wrote up how to use it with OpenFaaS, and gave a credit / link back to yourselves.

Web scraping that just works with OpenFaaS with Puppeteer

Just today an openfaas user reported seeing zombie chrome processes, so I built a test container to reproduce it:

docker run --name puppets -t -i -p 8080:8080 alexellis2/puppets:latest

curl localhost:8080
curl localhost:8080
curl localhost:8080
curl localhost:8080

[alex@nuc openfaas-puppeteer-template]$ docker exec -ti puppets ps -ef
UID          PID    PPID  C STIME TTY          TIME CMD
app            1       0  1 14:58 pts/0    00:00:00 fwatchdog
app           12       1  2 14:58 pts/0    00:00:00 node index.js
app           39       1  0 14:58 ?        00:00:00 [chrome] <defunct>
app           40       1  0 14:58 ?        00:00:00 [chrome] <defunct>
app           57       1  0 14:58 ?        00:00:00 [chrome] <defunct>
app           61       1  0 14:58 ?        00:00:00 [chrome] <defunct>
app           66       1  4 14:58 ?        00:00:00 [chrome] <defunct>
app          103       0 43 14:58 pts/1    00:00:00 ps -ef
[alex@nuc openfaas-puppeteer-template]$ 

This issue looks to be related:

puppeteer/puppeteer#1825

'use strict'
const assert = require('assert')
const puppeteer = require('puppeteer')

module.exports = async (event, context) => {
  let browser
  let page
  
  browser = await puppeteer.launch({
    args: [
      // Required for Docker version of Puppeteer
      '--no-sandbox',
      '--disable-setuid-sandbox',
      // This will write shared memory files into /tmp instead of /dev/shm,
      // because Docker’s default for /dev/shm is 64MB
      '--disable-dev-shm-usage'
    ]
  })

  const browserVersion = await browser.version()
  console.log(`Started ${browserVersion}`)
  page = await browser.newPage()
  let uri = "https://inlets.dev/blog/"
  if(event.body && event.body.uri) {
    uri = event.body.uri
  }

  const response = await page.goto(uri)
  console.log("OK","for",uri,response.ok())

  let title = await page.title()
  const result = {
    "title": title
  }

  await browser.close()

  // added recently, didn't change behaviour
  await browser.disconnect()
  
  return context
    .status(200)
    .succeed(result)
}

Would you have any suggestions for us? @toolmantim

Have you noticed similar issues yourself? (I didn't see anything in the issue tracker here, but Puppeteer appears to have many issues about it upstream)

So I copied the below section from your Dockerfile into mine to get puppeteer to work in my docker image. Is there any particular reason we are using google-chrome-unstable instead of the stable version?

RUN  apt-get update \
     # Install latest chrome dev package, which installs the necessary libs to
     # make the bundled version of Chromium that Puppeteer installs work.
     && apt-get install -y wget --no-install-recommends \
     && wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add - \
     && sh -c 'echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google.list' \
     && apt-get update \
     && apt-get install -y google-chrome-unstable --no-install-recommends \
     && rm -rf /var/lib/apt/lists/* \
     && wget --quiet https://raw.githubusercontent.com/vishnubob/wait-for-it/master/wait-for-it.sh -O /usr/sbin/wait-for-it.sh \
     && chmod +x /usr/sbin/wait-for-it.sh

Im little confused to choose between this docker image and https://hub.docker.com/r/alekzonder/puppeteer/dockerfile this image as my base image.

From my research, I came to know that node 10 had some under the hood V8 engine improvements for Chromium.

From performance point of view, Did you observe any difference when node 8 slim was used as base and changed to node 10?

Thanks 👍

I just wanted to know if this docker image "just works", because my experience with puppeteer has been, let's say, not exactly good. I understand dockerizing something so broke and laced with bugs could be a cumbersome task to say the least, and I can do nothing but appreciate you folks for attempting (and succeeding at) that!

Cheers.

Hi, since that Apple is moving to ARM, is there any chance for this image to provide a cross-arch image or a dedicated ARM one?

Doing a quick Google search this image is one of the first results, it seems to run Puppeteer on ARMv7, M1 is ARMv8-A so I'm not sure how different it is.
https://github.com/supernisor123/armv7-puppeteer/blob/master/Dockerfile

Could you please provide another build tag / Docker image for 2.1.1 as well? Seems the 2.x branch is missing.

Error: Failed to launch the browser process!
[0315/160314.126675:ERROR:zygote_host_impl_linux.cc(90)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.


TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

    at onClose (/usr/src/app/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:193:20)
    at Interface.<anonymous> (/usr/src/app/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:183:68)
    at Interface.emit (events.js:327:22)
    at Interface.close (readline.js:424:8)
    at Socket.onend (readline.js:202:10)
    at Socket.emit (events.js:327:22)
    at endReadableNT (internal/streams/readable.js:1327:12)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)
error Command failed with exit code 1.

I already tried everything but still the puppeteer is not running I am using macOSx catlina
I am passing the args as well

      args: [
        "--no-sandbox",
        "--disable-setuid-sandbox",
        // This will write shared memory files into /tmp instead of /dev/shm,
        // because Docker’s default for /dev/shm is 64MB
        "--disable-dev-shm-usage",
      ],

but still getting the same error tried with latest version and buildkite/puppeteer:7.1.0 as well

Hi. I built an image using this as a source.
However, an AST scan highlights this issue:
https://nvd.nist.gov/vuln/detail/CVE-2020-10878

How can this be fixed?

Whenever I call puppeteer from inside a Docker image based on this buildfile - I get this error:
(node:9) UnhandledPromiseRejectionWarning: Error: Failed to launch chrome!
[1125/075021.625772:FATAL:zygote_host_impl_linux.cc(116)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.

It's just a simple:
var browser = await puppeteer.launch({ headless: true });

On the provided link it says: IMPORTANT NOTE: The Linux SUID sandbox is almost but not completely removed.

So I'm not sure it's a viable strategy to use that - do you know a solution?

Since this is most likely going to be used for testing purposes, using just node allows for the most flexibility especially those that need node-gyp installed.

Hello,

Thank you for this library.
However, I have trouble. When I try your docker and I try to launch puppeteer, I have the following message,

In my package.json I have declared puppeteer with version 5.2.1. And I instantiate puppeteer with the following code
const browser = await puppeteer.launch({ args: [ // Required for Docker version of Puppeteer "--no-sandbox", "--disable-setuid-sandbox", // This will write shared memory files into /tmp instead of /dev/shm, // because Docker’s default for /dev/shm is 64MB "--disable-dev-shm-usage", ], });

Thank you for your support

Arcens

Trying to install something with apt is impossible.

FROM buildkite/puppeteer
RUN apt update && apt install git

Step 1/10 : FROM buildkite/puppeteer
 ---> 23a2e145eb22
Step 2/10 : WORKDIR /app
 ---> Using cache
 ---> 0c458cbc5821
Step 3/10 : RUN apt update && apt install git
 ---> Running in c1992790495f

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease
Get:2 http://security.debian.org/debian-security stretch/updates InRelease [94.3 kB]
Get:3 http://dl.google.com/linux/chrome/deb stable Release [943 B]
Get:4 http://dl.google.com/linux/chrome/deb stable Release.gpg [819 B]
Ign:5 http://deb.debian.org/debian stretch InRelease
Get:6 http://deb.debian.org/debian stretch-updates InRelease [91.0 kB]
Ign:4 http://dl.google.com/linux/chrome/deb stable Release.gpg
Get:7 http://deb.debian.org/debian stretch Release [118 kB]
Get:8 http://deb.debian.org/debian stretch Release.gpg [2410 B]
Get:9 http://security.debian.org/debian-security stretch/updates/main amd64 Packages [521 kB]
Get:10 http://deb.debian.org/debian stretch-updates/main amd64 Packages [27.9 kB]
Get:11 http://deb.debian.org/debian stretch/main amd64 Packages [7083 kB]
Reading package lists...
W: GPG error: http://dl.google.com/linux/chrome/deb stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 78BD65473CB3BD13
E: The repository 'http://dl.google.com/linux/chrome/deb stable Release' is not signed.
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-chrome-unstable.list:3 and /etc/apt/sources.list.d/google.list:1
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-chrome-unstable.list:3 and /etc/apt/sources.list.d/google.list:1

I'm building an image on top of buildkite/puppeteer:latest.
This is the Dockerfile

FROM buildkite/puppeteer:latest
ENV  PATH="${PATH}:/node_modules/.bin"
ADD  api api
RUN  cd api && yarn install
ADD  start.sh start.sh
RUN  apt-get update
RUN  apt-get upgrade -y
RUN  apt-get install -y git
RUN  apt-get install -y lsof
RUN  mkdir /root/.ssh
RUN  chmod 700 /root/.ssh
RUN  ######### irrelevant
ENV  ###### irrelevant
EXPOSE 3000
CMD  ./start.sh

This worked fine until yesterday evening, from then on following error appeared

W: The repository 'http://dl.google.com/linux/chrome/deb stable Release' does not have a Release file.
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-chrome-unstable.list:3 and /etc/apt/sources.list.d/google.list:1
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-chrome-unstable.list:3 and /etc/apt/sources.list.d/google.list:1
W: The repository 'http://security.debian.org/debian-security stretch/updates Release' does not have a Release file.
W: The repository 'http://deb.debian.org/debian stretch Release' does not have a Release file.
W: The repository 'http://deb.debian.org/debian stretch-updates Release' does not have a Release file.
E: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages  Error writing to output file - write (28: No space left on device) Error writing to file - write (28: No space left on device)
E: Failed to fetch http://security.debian.org/debian-security/dists/stretch/updates/main/binary-amd64/Packages  Error writing to output file - write (28: No space left on device) Error writing to file - write (28: No space left on device)
E: Failed to fetch http://deb.debian.org/debian/dists/stretch/main/binary-amd64/Packages  Error writing to output file - write (28: No space left on device) Error writing to file - write (28: No space left on device)
E: Failed to fetch http://deb.debian.org/debian/dists/stretch-updates/main/binary-amd64/Packages  Error writing to output file - write (28: No space left on device) Error writing to file - write (28: No space left on device)
E: Some index files failed to download. They have been ignored, or old ones used instead.
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-chrome-unstable.list:3 and /etc/apt/sources.list.d/google.list:1
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-chrome-unstable.list:3 and /etc/apt/sources.list.d/google.list:1

in the apt-get update step.

Going back to the image of v.1.11.0 fixed it. I'm not entirely sure if this is something you care about or you can fix.

While there is a release 1.16.0 of this repository, there is no docker image with the corresponding tag in the docker repository.

Is there any particular reason for this? Otherwise, would it be possible to push the docker image?

Hi,

I’m suddenly getting following error in my production pipeline (bitbucket):

Failed to launch chrome! /opt/atlassian/pipelines/agent/build/node_modules/puppeteer/.local-chromium/linux-686378/chrome-linux/chrome: error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory

I found a related issue in another project with the same problem:
atom/atom#13176

Any thoughts on what could be the issue with this image?

Thanks

I'm noticing failures when trying to install git via apt-get. The update is failing on github actions (https://github.com/exceptionless/Exceptionless.UI/runs/3484994833?check_suite_focus=true) when trying to do an apt-get update. This works locally on windows 10. Has anyone else ran into this?

FROM buildkite/puppeteer:10.0.0 AS base
WORKDIR /app

RUN apt-get update \
     && apt-get install -y git --no-install-recommends

Status: Downloaded newer image for buildkite/puppeteer:10.0.0
 ---> 764e9db1678f
Step 2/25 : WORKDIR /app
 ---> Running in 74dad1964bae
Removing intermediate container 74dad1964bae
 ---> e13f4e555ebd
Step 3/25 : RUN apt-get update      && apt-get install -y git --no-install-recommends
 ---> Running in 21abc8e3912c

Get:1 http://deb.debian.org/debian buster InRelease [122 kB]
Ign:2 http://dl.google.com/linux/chrome/deb stable InRelease
Get:3 http://deb.debian.org/debian buster-updates InRelease [51.9 kB]
Get:4 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
Err:5 http://dl.google.com/linux/chrome/deb stable Release
  404  Not Found [IP: 142.251.33.206 80]
Get:6 http://deb.debian.org/debian buster/main amd64 Packages [7907 kB]
Get:7 http://deb.debian.org/debian buster-updates/main amd64 Packages [15.2 kB]
Get:8 http://security.debian.org/debian-security buster/updates/main amd64 Packages [302 kB]
Reading package lists...
E: The repository 'http://dl.google.com/linux/chrome/deb stable Release' does not have a Release file.
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google.list:1
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google.list:1
The command '/bin/sh -c apt update      && apt-get update      && apt-get install -y git --no-install-recommends' returned a non-zero code: 100

PR created by bot:
#94

O.S: Windows 10
Version: latest
Code:

        const puppeteer = require('puppeteer');
        const browser = await puppeteer.launch({
            args: [
                '--no-sandbox',
                '--disable-setuid-sandbox',
                '--disable-dev-shm-usage'
            ]
        });
        const page = await browser.newPage();

Command: docker run --rm -v ~/app/:/app/ buildkite/puppeteer:latest node /app/index.js
Error:

(node:1) UnhandledPromiseRejectionWarning: TimeoutError: Timed out after 30000 ms while trying to connect to Chrome! The only Chrome revision guaranteed to work is r579032

I don't know if i'm running it propely as i'm new to docker :(

UnhandledPromiseRejectionWarning: Error: Could not find browser revision 737027