-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
在阿里云的容器服务里启动puppeteer启动报错 #7
Comments
是以Docker的方式启动的么?还是? |
如果以非Docker形式启动或不是以Mac系统启动的话,会有问题的,因为当初在设计程序的时候,没有打算考虑这种情况 |
是基于Docker的, 容器服务的介绍, Kubernetes里也试过,一样的问题 |
可以贴下你docker run的命令么,我在本地做个测试。 |
刚刚在本地使用: 测试没有问题,是自己构建的 |
这是容器日志
{"source":"Server","message":"Server running at http://127.0.0.1:80/","level":"info","hostname":"rebirth-0","material_url":"https://github.com/","timestamp":"2020-06-24 15:17:51"}
(node:21) UnhandledPromiseRejectionWarning: TimeoutError: Timed out after 30000 ms while trying to connect to Chrome! The only Chrome revision guaranteed to work is r706915
at Timeout.onTimeout (/etc/www/node_modules/puppeteer-core/lib/Launcher.js:359:14)
at listOnTimeout (internal/timers.js:549:17)
at processTimers (internal/timers.js:492:7)
(node:21) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag
--unhandled-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)(node:21) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
The text was updated successfully, but these errors were encountered: