clover/chrome repository overview

⁠Google Chrome docker image

This image is based on official Google Chrome build with debian libraries and it is built on top of clover/base⁠.

⁠Environment variables

* /opt/google/chrome/google-chrome is a wrapper around /opt/google/chrome/chrome binary that will be used by the chromedriver to launch the browser. It forcibly passes --headless and --disable-gpu arguments to the chrome binary. To override this behaviour pass /opt/google/chrome/chrome as a binary to the chromedriver:

ChromeOptions options = new ChromeOptions();
options.setBinary("/opt/google/chrome/chrome");

Wrapper also supports CHROME_ARGUMENTS environment variable to define additional (default) set of command line arguments. Each argument may be overidden if passed to the chromedriver:

options.addArguments("--window-size=1920,1080");

chromedriver does not close browsers on its own. If client craches before sending quit signal, browser will never be closed. To prevent this wrapper has CHROME_TIMEOUT environment variable that will set the execution cap of the chrome binary. This parameter is also available as an additional non-standard --process-timeout={seconds} command line argument. CHROME_TIMEOUT is not set by default. If set to any positive non-zero value will cap execution time of each browser separately, unless command line argument is specified:

options.addArguments("--process-timeout=60");

To disable execution time capping set it to zero (0).

** There are three options to launch chrome in the docker:

• as root user with --no-sandbox argument;
• as non-root user with SYS_ADMIN docker capability (--cap-add=SYS_ADMIN);
• as non-root user with --no-sandbox argument;

By default, chromedriver will be running as chrome user (PUID=50, PGID=50). To launch under root specify PUID=0, PGID=0. Custom PUID/PGID could be used to preserve data volume ownership on host.

⁠Exposed ports

⁠Supported platforms

• linux/amd64;