node.js - Puppeteer 错误 : Protocol error (Page. captureScreenshot):目标已关闭

Question

我在 node:8-slim 容器上运行 puppeteer@1.12.2 时遇到此错误。

完整的错误:

Error: Protocol error (Page.captureScreenshot): Target closed.
    at Promise (/app/node_modules/puppeteer/lib/Connection.js:183:56)
    at new Promise (<anonymous>)
    at CDPSession.send (/app/node_modules/puppeteer/lib/Connection.js:182:12)
    at Page._screenshotTask (/app/node_modules/puppeteer/lib/Page.js:903:39)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:189:7)
  -- ASYNC --
    at Page.<anonymous> (/app/node_modules/puppeteer/lib/helper.js:108:27)
    at /app/test.js:9:15
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:189:7)

js 文件(受 GoogleChrome/puppeteer/examples/screenshot.js 启发):

const puppeteer = require('puppeteer');
(async() => {
         const browser = await puppeteer.launch({
                headless: true,
                args: ['--no-sandbox', '--disable-setuid-sandbox', '--disable-gpu', '--disable-dev-shm-usage']
         });
          const page = await browser.newPage();
          await page.goto('http://google.com');
          await page.screenshot({path: 'example.png'});
          await browser.close();
})();

Dockerfile(受 troubleshooting.md#running-puppeteer-in-docker 启发):

FROM node:8-slim

RUN apt-get update && apt-get install -yq libgconf-2-4

RUN apt-get update && 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 fonts-ipafont-gothic fonts-wqy-zenhei fonts-thai-tlwg fonts-kacst ttf-freefont \
      --no-install-recommends \
    && rm -rf /var/lib/apt/lists/* \
    && apt-get purge --auto-remove -y curl \
    && rm -rf /src/*.deb

WORKDIR /app
RUN chown node: /app

user node

COPY ./ ./
RUN npm i --unsafe-perm=true

CMD ["node", "test.js"]

相同的 test.js 在主机操作系统上制作高质量的屏幕截图，但在容器中失败。

是否有任何神奇的参数可以在 node-slim 容器中运行它？我对任何版本的 puppeteer 都很满意。

从 Dockerfile 安装的 google-chrome-unstable 版本是“73.0.3683.20 dev”。 npm 安装的 chrome 版本为“73.0.3679.0”。

更新:

我已尝试将 await page.close() 添加为 Cody G.建议:

const puppeteer = require('puppeteer');
(async() => {
         const browser = await puppeteer.launch({
                headless: true,
                args: ['--no-sandbox', '--disable-setuid-sandbox', '--disable-gpu', '--disable-dev-shm-usage']
         });
          const page = await browser.newPage();
          await page.goto('http://google.com');
          await page.screenshot({path: 'example.png'});
          await page.close();
          await browser.close();
})();

这并没有太大区别。错误仍然在第 9 行 await page.screenshot 抛出，所以我猜它没有到达添加的行。

更新 2:

我添加了这样的事件记录器:

const puppeteer = require('puppeteer');
(async() => {
        try{
         const browser = await puppeteer.launch({
                headless: true,
                args: ['--no-sandbox', '--disable-setuid-sandbox', '--disable-gpu', '--disable-dev-shm-usage']
         });
          const page = await browser.newPage();
          const eventHandler = e=>(...args)=>console.log({e,args});
          for(let e of [
                  'close',
                  'console',
                  'dialog',
                  'domcontentloaded',
                  'error',
                  'frameattached',
                  'framedetached',
                  'framenavigated',
                  'load',
                  'metrics',
                  'pageerror',
                  'popup',
                  'request',
                  'requestfailed',
                  'requestfinished',
                  'response',
                  'workercreated',
                  'workerdestroyed'
          ]) {
                page.on(e, eventHandler(e));
          };
          await page.goto('http://google.com');
          await page.screenshot({path: 'example.png'});
          await page.close();
          await browser.close();
        } catch(e){
                console.error({e});
        }
})();

完整的日志很长，可在 https://gist.github.com/blex18/10ae4eed389ca818d72218baad3dfad2 获得.

基本上，经过几次重定向后，它到达了 https://www.google.com/?gws_rd=ssl其次是资源和 xhr 请求。

更新 3:

package.json:

{
  "name": "pup",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC",
  "dependencies": {
    "puppeteer": "^1.12.2"
  }
}

Docker 信息 1(不起作用):

Containers: 19
 Running: 3
 Paused: 0
 Stopped: 16
Images: 118
Server Version: 18.09.1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 205
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host ipvlan macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 9754871865f7fe2f4e74d43e2fc7ccd237edcbce
runc version: 96ec2177ae841256168fcf76954f7177af9446eb
init version: fec3683
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.15.0-45-generic
Operating System: Ubuntu 18.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 15.5GiB
Name: u4
ID: 3ZO4:OYYQ:K2X6:5QDB:ZNYO:FYNG:6YKT:HMDT:W3LX:UOY3:IEVU:3FCY
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Username: alex
Registry: https://index.docker.io/v1/
Labels:
Experimental: true
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false
Product License: Community Engine

WARNING: No swap limit support

Docker info 2(就像一个魅力)

Containers: 15
 Running: 6
 Paused: 0
 Stopped: 9
Images: 56
Server Version: 18.09.1
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host ipvlan macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 9754871865f7fe2f4e74d43e2fc7ccd237edcbce
runc version: 96ec2177ae841256168fcf76954f7177af9446eb
init version: fec3683
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.9.125-linuxkit
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 1.952GiB
Name: docker-desktop
ID: E3X5:BZUG:4QYZ:Z6EA:TBT4:Y36Z:ZQ5Y:ACZS:QAS2:7I6M:LGN7:J3GH
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 73
 Goroutines: 82
 System Time: 2019-02-13T10:04:59.482848Z
 EventsListeners: 2
HTTP Proxy: gateway.docker.internal:3128
HTTPS Proxy: gateway.docker.internal:3129
Registry: https://index.docker.io/v1/
Labels:
Experimental: true
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false
Product License: Community Engine

Answer 1

您的问题不可重现。它适用于我的 Centos 7，你的 Mac 环境，所以这似乎是 Docker 配置的问题，而不是代码的问题。可能的问题:

1. 使用的 docker 存储驱动程序:aufs 可能是个问题，尤其是对于较旧的内核和容器中的写入/删除操作；如果可能，请尝试默认 overlay2
2. 使用的安全配置文件:apparmor 和 seccomp 已启用，您可以尝试使用 --security-opt seccomp=unconfined 运行并检查dmesg，也许安全性阻止了某些事情