-
Notifications
You must be signed in to change notification settings - Fork 9k
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
can't run puppeteer in centos7 #391
Comments
Right in the error output. Did you go to the referenced page and read what it says about the problem and how to address it? |
@Garbee Thanks to replay yes,I read that page and try:
get some other error:
|
@paambaati I'm trying to install all this dependencies on centos 7, but nothing new install:
|
You need to convert the package names to be RHEL names. Those are only the Debian names. |
@Garbee I don't know how to convert, google them one by one ...? |
That or grab an RPM copy of the installer and use software management tools to look at what the dependencies of the package are. |
Having a similar issue. Here's what I discovered: [root@li583-175 chrome-linux]# ldd chrome | more I had installed one of the missing packages manually, but it still doesn't find it. I can see that particular package under /usr/lib/libpangocairo-1.0.so.0. |
So bottom of line , puppeteer can not work on centos ! |
Here's another issue I'm running into when trying on Docker Centos7: [root@3dd3c09a9d40 opt]# npm install -g puppeteer
Download failed: EACCES: permission denied, mkdir '/usr/lib/node_modules/puppeteer/.local-chromium'
I'm running as root. Not sure if that's the issue. I've changed ownership on that folder path. Even tried to create that folder manually and tried with sudo, yet I get that same error repeatedly. |
@rlog try install fonts?
|
Tried it in Ubuntu on Docker and got a similar message: root@6c5ca63ee50a:/opt/node_modules/puppeteer/.local-chromium/linux-494755/chrome-linux# ./chrome root@6c5ca63ee50a:/opt/node_modules/puppeteer/.local-chromium/linux-494755/chrome-linux# ldd ./chrome |
I am using centos 6.9 , is there any step by step guide to install "puppeteer" on ?
|
The best solution at this point is to use Ubuntu and follow these instructions #290 (comment). I started development on OSX and didn't realize about this issue until we decided to go into production 😮. |
@theoutlander Why install puppeteer globally in the first place? When installing globally and you're going into a non-user folder (as you are) you need to run as root. Hence why it is not recommended. |
@Garbee you're right! I was running into other installation issues and overlooked that I was installing globally. (I recall seeing it, but was thinking I need to install it globally) |
@Garbee kindly may you advice step by step for centos 6.X , i am very confused how to install ... |
@historylife Upgrade to CentOS 7. 6 is no longer supported. |
@Garbee i dont follow you , do you advise me to upgrade to CentOS 7. 6 |
@liulangyu90316 I have the same problem, centos7.3, I installed all the dependency but got |
which OS is recommend? I can change my OS (except macOS and Windows) |
@zhuyingda 's notes above will allow you to run puppeteer with The error message itself ('No usable sandbox!'), states Running without a sandbox should be considered bad practice and potentially harmful. Then again, if it works, it works. In recap: With that you'll be good to go (or should hopefully be), but it's playing a risky game, especially if this is a production system. (Out of curiosity I checked, and thankfully; you can't run |
If you're a lunatic you can spend a few days trying to compile chromium from source, then compile the sandbox from source, and attempt to monkey-patch them together. Although if you look at the top of the Build Sandbox link, it appears they'll be dumping support for the SUID sandbox in favor User namespaces sandbox (sandbox list). Here's the thing, it looks like the chromium issue for replacing SUID has been open since 2013 so I wouldn't bank on that fixing this. |
I have the same problem,too。 node:v8.4.0 (node:21521) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Failed to connect to chrome! |
@JustinYi922 You can try the font requirements which I mentioned |
I tried the yum install of all the dependencies mentioned in the troubleshooting doc and in this forum, and atk and gtk3 are no longer available. I had to find them elsewhere using rpm, so making use of puppeteer in production systems seems to be difficult. Is there anyway to resolve dependencies through package.json npm, I do not want to make customers do major installs to use a reports system as I try to replace phantomjs. |
Use docker
…On Thu, Jul 25, 2019 at 12:10 AM steve-powers ***@***.***> wrote:
I tried the yum install of all the dependencies mentioned in the
troubleshooting doc and in this forum, and atk and gtk3 are no longer
available. I had to find them elsewhere using rpm, so making use of
puppeteer in production systems seems to be difficult. Is there anyway to
resolve dependencies through package.json npm, I do not want to make
customers do major installs to use a reports system as I try to replace
phantomjs.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#391>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABQXS2G6A5WQJDM5RTA3G3QBCEHJANCNFSM4DXRNURQ>
.
--
With Best Regards,
Constantine
|
Seems so convoluted. I hope you can get it working on CentOS 7. I managed to do it a month or so back. Actually had to switch servers and upgrade from CentOS 6 to run Puppeteer. |
I have been trying to get non-docker centos7 puppeteer working and originally was running a big series of yum+rpm I found, which I complained about here. But combing through again I was able to use the solution last appended by jjejj on Mar 12, so edited this append. |
Try sudo yum install -y chromium then run npm I again and run your app. |
Hope this helps for you , it resolved my issue. |
thanks ! |
Thanks @Sanjay007 !!
This solved my problem with the sandbox too!
Please update the docs on the sandbox for the current advise is not working at all in Centos7. |
@
Thanks god your fix work on my env, i'm on centos 7.8 using taiko |
have you solved this problem? i faced this issue too |
In our case (Amazon Linux 2) we fixed it by:
As explained in the docs: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md#chrome-headless-doesnt-launch-on-unix Hope that helps someone. |
On a barebones install of CentOS 7 (on Amazon AWS EC2), I was able to get chrome headless running with the following: |
For anybody trying to get puppeteer to work on a
|
keepping focus |
My environment:
After executing the command mentioned in the link below, it no longer prompts that
Later you may encounter "No sandbox available!", you can check this link: If the above method does not work, it is recommended to read the troubleshooting document and try it, it should help: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md |
thank you very much |
I tried installing the packages individually as it complained, but it wouldn't update. Thanks for this. |
This worked for me
|
@kapraran for me, this worked too on Amazon Linux |
Server Info:
CUP: Intel(R) Xeon(R) Platinum 8163 CPU @ 2.50GHz
MemTotal: 1016396 kB
OS:CentOS Linux release 7.3.1611 (Core)
Node:v8.4.0
when I try to run my app in this server, there have an error throw:
I want run Chromium which download by puppeteer manual,there have some log output:
pls help,how to fix this ?
The text was updated successfully, but these errors were encountered: