Puppeteer cannot start chrome

[wotaen]

Issue details

When using storyshots and imageSnapshot:

initStoryshots({suite: 'Image storyshots', test: imageSnapshot({storybookUrl: 'http://localhost:9001'})});

headless chrome process is started, but jest cannot connect to it, first error:

Timeout - Async callback was not invoked within the 5000ms timeout specified by jest.setTimeout.

However, when I change this line in test-body-image-snapshot.js:
.launch({ args: ['--no-sandbox ', '--disable-setuid-sandbox'] })
to
.launch({execPath: '/usr/bin/chrome'}) where /usr/bin/chrome is headless chrome driver, everything works as expected.

Please specify which version of Storybook and optionally any affected addons that you're running

storybook/addon-storyshots: ^3.4.0-alpha.9,

Affected platforms

• Ubuntu, 14.04

[danielduan]

I wonder if this is a problem with different Linux distros and the configs of the binarys. We do run it on a docker image with Linux and it seems to work fine.

[stale]

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

[Hypnosphi]

Note that we also run this command before visual tests on CLI:

https://github.com/storybooks/storybook/blob/master/scripts/workaround-puppeteer-issue-290.sh

[stale]

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

[stale]

Hey there, it's me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please open a new ticket and mention this old one. Cheers and thanks for using Storybook!

[EdenTurgeman]

I also just encountered this problem, would love to find out a solution.