Question

我正在使用Node.js 10 我正在尝试使用伪装者创建PDF。这是docker文件

FROM node:10-alpine

RUN echo "http://dl-2.alpinelinux.org/alpine/edge/main" > /etc/apk/repositories
RUN echo "http://dl-2.alpinelinux.org/alpine/edge/community" >> /etc/apk/repositories
RUN echo "http://dl-2.alpinelinux.org/alpine/edge/testing" >> /etc/apk/repositories

ENV CHROME_BIN="/usr/bin/chromium-browser" \
    PUPPETEER_SKIP_CHROMIUM_DOWNLOAD="true"

RUN set -x \
    && apk update \
    && apk upgrade \
    && apk add --no-cache \
    udev \
    ttf-freefont \
    chromium \
    && npm install puppeteer@1.17.0

RUN mkdir -p /home/node/app/node_modules && chown -R node:node /home/node/app

WORKDIR /home/node/app

ENV PATH /home/node/app/node_modules/.bin:$PATH

COPY package*.json ./

RUN apk --no-cache --virtual build-dependencies add \
    python \
    make \
    g++ \
    && npm install \
    && apk del build-dependencies

USER node

RUN npm install

RUN mkdir -p /home/node/app/logs

COPY --chown=node:node . .

EXPOSE 4000

EXPOSE 3050

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

尝试启动浏览器实例时出现以下错误。

{ Error: Protocol error (IO.read): Invalid parameters handle: string value expected
    at Promise (/home/node/app/node_modules/puppeteer/lib/Connection.js:183:56)
    at new Promise (<anonymous>)
    at CDPSession.send (/home/node/app/node_modules/puppeteer/lib/Connection.js:182:12)
    at Function.readProtocolStream (/home/node/app/node_modules/puppeteer/lib/helper.js:241:37)
    at Page.pdf (/home/node/app/node_modules/puppeteer/lib/Page.js:988:25)
    at process._tickCallback (internal/process/next_tick.js:68:7)
  -- ASYNC --
    at Page.<anonymous> (/home/node/app/node_modules/puppeteer/lib/helper.js:111:15)
    at fetchLedgerPdf (/home/node/app/Models/post/pdfCreation.js:316:39)
    at process._tickCallback (internal/process/next_tick.js:68:7)
  message:
   'Protocol error (IO.read): Invalid parameters handle: string value expected' }

我确保我的铬和木偶版本与许多论坛上提到的相同。我正在使用puppeteer@1.17.0，并使用使用铬76.0.3809.132-r0的阿尔卑斯山边缘图像。我也尝试过使用puppeeteer@1.18.0，但问题仍然存在

Answer 1

我能够通过从该图片创建容器来解决此问题， Browserless Chrome 该图像处理了所有依赖关系，并且操纵up的人很迷人。我建议使用此映像，而不是手动添加依赖项。

无法在Docker映像中启动puppeteer浏览器实例

1 个答案: