bonigarcia/webdrivermanager

By bonigarcia

Updated 23 days ago

Automatic management of Selenium WebDriver binaries

Image
1

50K+

bonigarcia/webdrivermanager repository overview

WebDriverManager can be used as a Docker container to execute the Server and CLI (Command Line Interface) modes. To execute WebDriverManager Server in Docker, you simply need to run the following command:

docker run --rm -p 4444:4444 -v /var/run/docker.sock:/var/run/docker.sock bonigarcia/webdrivermanager:5.1.0

To execute WebDriverManager CLI in Docker, you need to specify the type of browser to be resolved using the argument resolveDriverFor, passes as an environmental variable using ARGS. The rest of WebDriverManager configuration parameters can be passed to the Docker container using env variables using the usual -e option in Docker. For example, for Chrome (i.e., to resolve chromedriver):

docker run --rm -v ${PWD}:/wdm -e ARGS="resolveDriverFor chrome" bonigarcia/webdrivermanager:5.1.0

To execute browsers in Docker containers and interact with them using noVNC, you need to specify the argument runInDocker, as follows :

docker run --rm -it -v /var/run/docker.sock:/var/run/docker.sock -e ARGS="runInDocker chrome 91" bonigarcia/webdrivermanager:5.1.0

Tag summary

Content type

Image

Digest

sha256:a135af65a

Size

140.5 MB

Last updated

23 days ago

Requires Docker Desktop 4.37.1 or later.