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
ERROR:zygote_host_impl_linux.cc(89)] Running as root without --no-sandbox is not supported #3698
Comments
@arkreddy I'm not sure what's going on here. How do I reproduce this? Also, I'd strongly recommend against running Chrome as root. If you're inside docker, I'd recommend using a non-root user instead. |
@aslushnikov: You (graphically) login as root, and try starting chrome or chromium. Happens when you use Chrome/Chromium or libQt5WebEngineCore, or anything else based on Chromium Embedded in an application.
vs.
but only if the logged-in user is root (uid 0). |
@ststeiger so which are the puppetteer.launch({
headless: true,
args: ['--no-sandbox']
}) Or do I need to add args: |
--no-sandbox is sufficient, AFAIK. |
@ststeiger I'm still getting the launch error on Ubuntu 18.09 when only using The full stack trace is
|
[UPDATE]
(taken from https://hub.docker.com/r/browserless/chrome/) But I'm now getting the Running as root without --no-sandbox is not supported
|
This worked for me |
A i see, dependency problem. |
I have all the dependency problems and still get the error |
thanks for the advice, check and let you know |
I am still getting below error even after setting up the sandbox by following instructions in the troubleshooting page: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md (node:5910) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 6): Error: Failed to launch chrome! OS details AME="Ubuntu" Waiting for a quick response Thanks |
If there was a way to set --no-sandbox through an environment variable, that would provide a solution to piqnt/svgexport#76 ; that, or an automatic check for root/docker and adding this to the default set of arguments. |
I have a problem |
Try running it again without root privileges. In my case that's what it
was. Do some research to change the code. I forgot which file in
particular. I believe Because sandbox is not supported headless anymore. I
could be wrong.
…On Tue, Mar 24, 2020, 7:49 PM Hemershon Silva ***@***.***> wrote:
I have a problem
[6479:0324/204738.124259:FATAL:atom_main_delegate.cc(210)] Running as root
without --no-sandbox is not supported. See https://crbug.com/638180.
Trace/breakpoint trap
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3698 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGB7MGAJKZFYXK5ALEJ4TIDRJFBKLANCNFSM4GLU7BOA>
.
|
https://unix.stackexchange.com/questions/175967/how-to-run-google-chrome-as-root-in-linux
It's not supported running it as root.
…On Tue, Mar 24, 2020, 7:49 PM Hemershon Silva ***@***.***> wrote:
I have a problem
[6479:0324/204738.124259:FATAL:atom_main_delegate.cc(210)] Running as root
without --no-sandbox is not supported. See https://crbug.com/638180.
Trace/breakpoint trap
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3698 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGB7MGAJKZFYXK5ALEJ4TIDRJFBKLANCNFSM4GLU7BOA>
.
|
… On Tue, Mar 24, 2020, 7:49 PM Hemershon Silva ***@***.***> wrote:
I have a problem
[6479:0324/204738.124259:FATAL:atom_main_delegate.cc(210)] Running as root
without --no-sandbox is not supported. See https://crbug.com/638180.
Trace/breakpoint trap
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3698 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGB7MGAJKZFYXK5ALEJ4TIDRJFBKLANCNFSM4GLU7BOA>
.
|
When i am putting headless: true, it is working perfectly fine. TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md
.js:179:65) |
I got the same problem after upgrading my ubuntu from 18.04.5 to 20.04.1 on chromium(default browser). Chrome is working fine but chromium is not opening.
|
Hii, thanks. The problem is now fixed. I also upgraded my ubuntu to fix it. 😊 |
no sandbox solved this issue for me in amazon ec2 linux instance |
use this it worked for me new Client({puppeteer: { headless: true ,args: ['--no-sandbox','--disable-setuid-sandbox'] }}); |
Got this error when running apt-get update && apt-get install -y gconf-service libasound2 libatk1.0-0 libc6 libcairo2 libcups2 libdbus-1-3 libexpat1 libfontconfig1 libgcc1 libgconf-2-4 libgdk-pixbuf2.0-0 libglib2.0-0 libgtk-3-0 libnspr4 libpango-1.0-0 libpangocairo-1.0-0 libstdc++6 libx11-6 libx11-xcb1 libxcb1 libxcomposite1 libxcursor1 libxdamage1 libxext6 libxfixes3 libxi6 libxrandr2 libxrender1 libxss1 libxtst6 ca-certificates fonts-liberation libappindicator1 libnss3 lsb-release xdg-utils wget libgbm1 To fix the sandbox error I used this line in my script: const browser = await puppeteer.launch({headless: true, args: ['--no-sandbox']}); UPDATE: the full list of dependencies for Ubuntu is here and apparently you can get it by running |
This worked for me by adding |
Switch to Simple User and then run the command |
I heed help!!! /app/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:241 |
The problem continue in Digital Ocean Apps. Ideas?
|
In my case i was trying to use a R Studio library that uses Google Chrome during the code running, so I tried uninstalling completely Google Chrome, restarting my Virtual Machine and running it again, and installing Chrome again following these steps: Hope this helps someone in a similar situation like me. |
Error: Unable to launch browser, error message: Failed to launch the browser process! Ubuntu 22.04.1 LTS (GNU/Linux 5.15.0-1031-aws x86_64) |
Even with the flag no-sandbox still says the same error. I saw another issue with that flagged. |
Steps to reproduce
Tell us about your environment:
Chrome version: 71.0.3578.98-1 Channel: stable
OS Version: Debian GNU/Linux 8 (jessie)
Flash Version:
What steps will reproduce the problem?
Steps to reproduce the problem:
15:40:19 Error: Failed to launch chrome!
15:40:19 [1220/234018.696360:ERROR:zygote_host_impl_linux.cc(89)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
15:40:19
15:40:19
15:40:19 TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
15:40:19
The code snippet:
const puppeteer = require('puppeteer');
describe(' SC Station Test', () => {
test(
Station Scan Test
, async () => {browser = await puppeteer.launch({args: ['--no-sandbox']});
page = await browser.newPage();
await page.goto("https://www.google.com/")
await browser.close();
}, 20000);
});
What is the expected behavior?
It should able launch the headless browser and able ot execute the tests
What went wrong?
Did this work before? It didn't
The text was updated successfully, but these errors were encountered: