-
Notifications
You must be signed in to change notification settings - Fork 30
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 with running stress #14
Comments
Hi, |
Hi, |
Hi @06dilipg, You can rely on some part of script I did few months ago which worked for me (did not test it recently) :
This script is based on this file |
Hi @Fry-4TF1V, All the above configurations are done. At the end, when i give the command "make stress" i'm getting below error: ERROR: Couldn't connect to Docker daemon at http+docker://localhost - is it running? If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable. FYI: I'm installing the bbb-stress-test in different server and bigbluebutton is installed in different server. |
How I can run this? root@localhost:/tmp/bbb-stress-test# make stress TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/master/docs/troubleshooting.md
|
Had the same issue, I edited the file lib/stress-test.js, added de arg "--no-sandbox" in the array declared on line 80: Not sure if that was the best but it worked, now I'm facing the error mentioned here: #11 |
I had the same problem, if you follow this steps to make it possible to run docker as non-root, and then go back to the very beginning to build the image and run the tests, everything works fine |
Hi there,
I have install the package by the mentioned instructions. But when a I am going to run the "make stress" the following error has appeared.
Error: Failed to launch the browser process!
[0510/195146.876103:ERROR:zygote_host_impl_linux.cc(90)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
I will be so grateful if you guide me how I can resolve this error.
thank you.
The text was updated successfully, but these errors were encountered: