|
| 1 | +[docker] |
| 2 | +# Configs have a mapping between the Docker image to use and the capabilities that need to be matched to |
| 3 | +# start a container with the given image. |
| 4 | +configs = [ |
| 5 | + "seleniarm/node-firefox:latest", '{"browserName": "firefox"}', |
| 6 | + "seleniarm/node-chromium:latest", '{"browserName": "chrome"}', |
| 7 | +] |
| 8 | + |
| 9 | +# URL for connecting to the docker daemon |
| 10 | +# Most simple approach, leave it as http://127.0.0.1:2375, and mount /var/run/docker.sock. |
| 11 | +# 127.0.0.1 is used because internally the container uses socat when /var/run/docker.sock is mounted |
| 12 | +# If var/run/docker.sock is not mounted: |
| 13 | +# Windows: make sure Docker Desktop exposes the daemon via tcp, and use http://host.docker.internal:2375. |
| 14 | +# macOS: install socat and run the following command, socat -4 TCP-LISTEN:2375,fork UNIX-CONNECT:/var/run/docker.sock, |
| 15 | +# then use http://host.docker.internal:2375. |
| 16 | +# Linux: varies from machine to machine, please mount /var/run/docker.sock. If this does not work, please create an issue. |
| 17 | +url = "http://127.0.0.1:2375" |
| 18 | +# Docker image used for video recording |
| 19 | +video-image = "selenium/video:latest" |
| 20 | + |
| 21 | +# Uncomment the following section if you are running the node on a separate VM |
| 22 | +# Fill out the placeholders with appropriate values |
| 23 | +#[server] |
| 24 | +#host = <ip-from-node-machine> |
| 25 | +#port = <port-from-node-machine> |
0 commit comments