This repository has been archived by the owner on Sep 1, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 33
Running in Bitbucket pipeline: --no-sandbox #51
Comments
I got passed the '--no-sandbox' error by using the a temp sudo user like above, but that wasn't quite the right script, here is the script:
|
Did you also find a way to pass |
@skeggse I actually never got it working. We ended up having to bypass. :( The above code bypasses the no-sandbox but there were several other layers we kept running into. |
For future reference, electron supports a |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am trying to run test through out pipeline in Bitbucket. I keep hitting this error:
[973:1011/205026.940590:FATAL:atom_main_delegate.cc(210)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
Is there a way to pass the --no-sandbox flag through? Or use a user other than root? Or maybe some other solution?
I tried this:
adduser temp && adduser temp sudo && su - temp && yarn test
but I am the first to admit I am not a Systems person.
-- Update:
I am passed that one, but am now hitting an error that says
(electron:987): Gtk-WARNING **: cannot open display:
that I can't seem to get around.-- another update:
I am passed that one, and am now hitting
xhost: unable to open display ":0.0"
:sigh:The text was updated successfully, but these errors were encountered: