You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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:
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?
The text was updated successfully, but these errors were encountered: