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在主机OS上生成高质量的屏幕截图，但在容器中失败。

在node-slim容器中是否有任何魔术参数可以运行它？我对能使用任何版本的木偶感到满意。

从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信息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

我可以为您提供解决方案

    FROM node:8-slim

# See https://crbug.com/795759
RUN apt-get update && apt-get install -yq libgconf-2-4

# Install latest chrome dev package and fonts to support major charsets (Chinese, Japanese, Arabic, Hebrew, Thai and a few others)
# Note: this installs the necessary libs to make the bundled version of Chromium that Puppeteer
# installs, work.
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

# It's a good idea to use dumb-init to help prevent zombie chrome processes.
ADD https://github.com/Yelp/dumb-init/releases/download/v1.2.0/dumb-init_1.2.0_amd64 /usr/local/bin/dumb-init
RUN chmod +x /usr/local/bin/dumb-init

# Uncomment to skip the chromium download when installing puppeteer. If you do,
# you'll need to launch puppeteer with:
#     browser.launch({executablePath: 'google-chrome-unstable'})
# ENV PUPPETEER_SKIP_CHROMIUM_DOWNLOAD true

# Install puppeteer so it's available in the container.
RUN npm i puppeteer

# Add user so we don't need --no-sandbox.
RUN groupadd -r pptruser && useradd -r -g pptruser -G audio,video pptruser \
    && mkdir -p /home/pptruser/Downloads \
    && chown -R pptruser:pptruser /home/pptruser \
    && chown -R pptruser:pptruser /node_modules

# Run everything after as non-privileged user.
USER pptruser

ENTRYPOINT ["dumb-init", "--"]
CMD ["google-chrome-unstable"]

这是迄今为止我发现基于rpm的系统的google-chrome-stable最好的镜像。

http://orion.lcg.ufrj.br/RPMS/myrpms/google/

Answer 2

您的问题不可复制。它可以在我的Mac环境下的Centos 7上运行，因此这似乎与Docker配置有关，而与代码无关。可能的问题：

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

Answer 3

我可以重现这个问题。

这是我的代码

browser = await puppeteer.launch({
      defaultViewport:{width:1920,height:6000},
      headless: true,
      executablePath: await chromium.executablePath,
      args: chromium.args,
      ignoreDefaultArgs: ["--hide-scrollbars"],
    });

let siteName = urlArray[urlIndex].split('://')[1];
      const page = await browser.newPage();
      await page.goto(urlArray[urlIndex], {
        waitUntil: ['domcontentloaded', 'networkidle0', 'networkidle2'],
      });
      
      const buffer = await page.screenshot({
          clip: { x: 0, y: 0, width:1920, height: 6000}
      });
      result = await page.title();

错误

START RequestId：51ec6b89-6c49-408d-95e1-f09492e1ecee 版本：$LATEST 2021-06-04T14:12:05.738Z 51ec6b89-6c49-408d-95e1-f09492e1ecee ERROR 错误：导航失败，因为浏览器已断开连接！在 CDPSession.LifecycleWatcher._eventListeners.helper.addEventListener (/opt/nodejs/node_modules/puppeteer-core/lib/LifecycleWatcher.js:46:107) 在 CDPSession.emit (events.js:198:13)

或

错误：协议错误（Page.captureScreenshot）：目标已关闭

解决方案 由于屏幕截图的高度和宽度，我遇到了问题。我的页面太长，所以我需要将屏幕截图的高度增加到 6000，这导致浏览器断开连接或协议错误。此外，我使用相同的浏览器对象截取了导致上述问题的 4 个网站。

所以，我在截图之前重新初始化了浏览器对象，如下所示：

for (let urlIndex = 0; urlIndex < urlArray.length; urlIndex++) {
    try {
      browser = await puppeteer.launch({
        defaultViewport:{width:1920,height:6000},
        headless: true,
        executablePath: await chromium.executablePath,
        args: chromium.args,
        ignoreDefaultArgs: ["--hide-scrollbars"],
      });

它解决了我的问题。

Answer 4

这里有两个选择

您是否尝试像Puppeteer中的文档一样更新Dockerfile？

https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md#running-puppeteer-in-docker

尝试在Dockerfile中使用旧版本（http://dl.google.com/linux/chrome/deb/stablemain）更改chrome Linux。由于chrome稳定版本已更新，因此无法适应puppeteer的旧版本，因此我尝试找到旧版本的Chrome，但是：D

谢谢

木偶错误：协议错误（Page.captureScreenshot）：目标已关闭

4 个答案: