Closed ghost closed 7 years ago
Unfortunately in some docker images it causes chrome crash, and the only way to fix it is to pass --privileged
to docker run command.
For this case I would rather add possibility to add any extra argument to chrome executable.
Good point. I created a second pull request that is more generic.
The Chrome/Chromium sandbox currently does not work within a Docker container. Adding --no-sandbox as one of the command line options allows Chrome/Chromium to execute properly within a Docker container.