Patrick Hulce

thanks for the feedback @nathanboktae, these docs used to be more closely tied to the ones in Lighthouse that reference getting setup in CI/docker environments this [dockerfile](https://github.com/ebidel/lighthouse-ci/blob/master/builder/Dockerfile.headless) was once linked...

@jakelacey2012 what does `resp.body` actually look like in that script? You're passing `undefined` to puppeteer as the websocket URL so something is amiss.

@jakelacey2012 that means you're using a version of chrome that's not compatible with the version of puppeteer you're using. Each version of puppeteer is meant to be used with a...

Puppeteer automatically downloads a compatible version and sticks it in your node_modules for you, this is what it will use by default. Either way I suggest you find help over...

@kyasbal-1994 the [lighthouse-ci docs](https://github.com/GoogleChrome/lighthouse-ci/tree/master/docs/recipes/docker-client#--no-sandbox-issues-explained) have a decent explanation of the tradeoffs involved in `--no-sandbox` and the different workarounds.

Thanks for filing @pcgeek86! As a general rule we won't be able to resolve every Chrome installation which is why the `CHROME_PATH` environment variable exists. If this is a pretty...

@calebeby see https://github.com/GoogleChrome/chrome-launcher/pull/68#issuecomment-377825645, if you'd like to be the one to pick it up, be our guest :)

This flag is still in use in the Chromium codebase [AFAICT](https://cs.chromium.org/search/?q=kDisableSetuidSandbox&sq=package:chromium&type=cs), so we would like to continue supporting it, but we've added `ignoreDefaultFlags` as a way to disable other default...

Thanks for filing! Q: You're using headful Chrome, correct? If so, why not headless? Q: If you're using puppeteer, what led you to use `chrome-launcher` over `puppeteer.launch`? I'm not aware...

I'm not aware of any better ways than the flags you've documented and the autoplay audio and video hacks unfortunately :/