alihan/docker-selenium-grid
1
0
Fork 0
mirror of https://github.com/SeleniumHQ/docker-selenium.git synced 2024-02-23 15:49:32 +03:00
Code Issues Projects Releases Wiki Activity

Fix environment variable naming in README (#1761)

Browse Source
This commit is contained in:
Marvin A. Ruder
2023-01-03 04:27:20 +01:00
committed by GitHub
parent 7863a8409a
commit b6d5b1efcf
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@@ -844,12 +844,12 @@ captured in the same video.
[Chrome](https://developers.google.com/web/updates/2017/04/headless-chrome),
When using headless mode, there's no need for the [Xvfb](https://en.wikipedia.org/wiki/Xvfb) server to be started.
To avoid starting the server you can set the `SE_START_XVFB` environment variable to `false`
To avoid starting the server you can set the `START_XVFB` environment variable to `false`
(or any other value than `true`), for example:
``` bash
$ docker run -d --net grid -e SE_EVENT_BUS_HOST=selenium-hub -e SE_EVENT_BUS_PUBLISH_PORT=4442 \
-e SE_EVENT_BUS_SUBSCRIBE_PORT=4443 -e SE_START_XVFB=false --shm-size="2g" selenium/node-chrome:4.7.2-20221219
-e SE_EVENT_BUS_SUBSCRIBE_PORT=4443 -e START_XVFB=false --shm-size="2g" selenium/node-chrome:4.7.2-20221219
```
For more information, see this GitHub [issue](https://github.com/SeleniumHQ/docker-selenium/issues/567).
@@ -1204,7 +1204,7 @@ or
`Message: unknown error: Chrome failed to start: exited abnormally`
The reason _might_ be that you've set the `SE_START_XVFB` environment variable to "false", but forgot to
The reason _might_ be that you've set the `START_XVFB` environment variable to "false", but forgot to
actually run Firefox, Chrome or Edge in headless mode.
### Mounting volumes to retrieve downloaded files