Support launching in Docker

We have a CI environment at my company that does not have chrome nor allows apt-get install on our machines, but docker is available for better isolation of these dependencies, but I see no documentation or support for Docker. This would be greatly appreciated. I’m trying to get a shell script put together that can achieve this by passing in as a CHROME_PATH, which may be the best, most unobtrustive way to support it. I’m struggling to get it working though 😕

[kyasbal]

I struggled with the relevant issue for a while.

This is my code to launch Chrome in headless mode in Docker.

function getChromeFlags(resolution: Resolution2D) {
  let appendedOptions = headless ? ["--headless", "--disable-gpu"] : [];
  return [
    `--window-size=${resolution.width},${resolution.height}`,
    ...appendedOptions
  ];
}
const chrome = await ChromeLauncher.launch({
  startingUrl: url,
  chromeFlags: getChromeFlags(resolution)
});

Then I got this error.

{ Error: connect ECONNREFUSED 127.0.0.1:46803
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1107:14)
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '127.0.0.1',
  port: 46803 }

I tried to use puppeteer workaround that @jakelacey2012 suggested. But actually that won’t work for me.

I could solve this problem by adding --no-sandbox flag as chromeFlags in the launch option.

I hope this workaround is still safe for most of CI use case.

[patrickhulce]

@kyasbal-1994 the lighthouse-ci docs have a decent explanation of the tradeoffs involved in --no-sandbox and the different workarounds.