I recently started an attempt to upgrade some existing testing setups to Circle 2.0, and am running into a problem getting Chrome to start. The project is an Ember project, and the tests are run in Chrome with the help of
testem, using the
circleci/node:4.8-browsers base image.
When attempting to start Chrome, the following error occurs:
Error: Browser exited unexpectedly Non-zero exit code: 1 Stderr: [0727/183643.547535:ERROR:nacl_helper_linux.cc(311)] NaCl helper process running without a sandbox! Most likely you need to configure your SUID sandbox correctly
Some Googling seemed to indicated that providing some combination of
--user-data-dir would circumvent this issue, but I have had no success with any combination of the above.
To rule out other issues with the environment, I removed all other steps except an experimental “Start Chrome” step, which also fails. However, this step does not seem to output the reason why. When using ssh to debug, the same error is shown.
I even went so far as to pull down the
circleci/node:4.8-browsers image locally, to attempt to reproduce the error there, but ran into some issues with X server, so was unable to reproduce it locally.
I also dug up a previous attempt at the circle upgrade by one of my coworkers, and re-ran that against the current circle configuration. The previous builds were passing, but a large number of tests had been skipped (my reason for starting from a blank state). However, after a rebuild (without cache, to address a build tooling issue), the previously-passing branch is now failing with the same problem my branch is having.
Any thoughts on what the issue might be? I believe the version of Chrome in this image is a newer version than when the previous attempt to do this migration, so it could be related to the version of Chrome installed.
[Edit] I tried a couple other images from the circleci/node tags list, and discovered that
circleci/node:4.8.4-browsers seem to work, but
circleci/node:4.8-browsers do not. My hunch was that something is misconfigured from the builds that are tagged as having been updated “14 days ago”. However, this little experiment seems to have ruled out the timing aspect.