ChromeHeadless can't run as root with --no-sandbox anymore

[boboldehampsink]

After updating to Chrome 62 and Chromedriver 2.33, I get the following error when running karma tests with ChromeHeadless:

  | 25 10 2017 08:47:40.197:ERROR [launcher]: Cannot start ChromeHeadless
  | [1025/084740.006078:ERROR:zygote_host_impl_linux.cc(88)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.

This is in Docker running Ubuntu 16

[boboldehampsink]

Workaround:

    browsers: ['ChromeHeadlessNoSandbox'],
    customLaunchers: {
      ChromeHeadlessNoSandbox: {
        base: 'ChromeHeadless',
        flags: ['--no-sandbox']
      }
    },

[tariqbuilds]

@boboldehampsink Is it assumed that your actual configuration also has --headless and --remote-debugging=9222 in the flags array?

[boboldehampsink]

When specifying the browser as ChromeHeadless this is automatically added, yes.

[tariqbuilds]

This worked for us. Thanks, @boboldehampsink

[sebastian-burdun]

Worked for me too. Thanks.

[germs12]

Worked for me too. Thanks guys!

Keywords: CodeBuild, Karma, Chrome

[myluckagain]

boboldehampsink, sorry, but where should this workaround be written? Is it about docker?

[boboldehampsink]

In karma config

[DragonRus]

Sorry for the rookie question: and where should I put this text?

browsers: ['ChromeHeadlessNoSandbox'],
customLaunchers: {
ChromeHeadlessNoSandbox: {
base: 'ChromeHeadless',
flags: ['--no-sandbox']
}
},

Where is this karma config?

[alexbainter]

@DragonRus By default, most projects have Karma configuration stored in a file named "karma.conf.js." However, that is just the default; the configuration file could be named anything and passed to Karma like this: karma start some-karma-config.js.

If your project doesn't have a configuration file, you can generate it by running karma init from a command line. See the Karma documentation.

[oliversalzburg]

I was not aware of the ability to define custom launchers. I would consider it very helpful if this was added to the README.