How are you controlling headless Chrome when it's running in a Docker?

[vg-pulsepoint]

Most of the tutorials use the chromedriver to control chrome, which explicitly points to the binary file. How do you programmatically control Chrome when it runs remotely in a Docker?

[caryyu]

@vg-pulsepoint see https://hub.docker.com/r/caryyu/selenium-chrome/

[justinribeiro]

I control Chrome through the container primarily via Chrome Debugging Protocol and port 9222. I do this via https://github.com/cyrus-and/chrome-remote-interface which you can script. To show this in action, I fired up the REPL in screenshot below:

If you're looking for Selenium WebDriver support, @yukinying has a version (https://github.com/yukinying/chrome-headless-browser-docker) that builds on top of the official docker-selenium image.