Skip to content

Commit b6d5b1e

Browse files
authored
Fix environment variable naming in README (#1761)
1 parent 7863a84 commit b6d5b1e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -844,12 +844,12 @@ captured in the same video.
844844
[Chrome](https://developers.google.com/web/updates/2017/04/headless-chrome),
845845
When using headless mode, there's no need for the [Xvfb](https://en.wikipedia.org/wiki/Xvfb) server to be started.
846846

847-
To avoid starting the server you can set the `SE_START_XVFB` environment variable to `false`
847+
To avoid starting the server you can set the `START_XVFB` environment variable to `false`
848848
(or any other value than `true`), for example:
849849

850850
``` bash
851851
$ docker run -d --net grid -e SE_EVENT_BUS_HOST=selenium-hub -e SE_EVENT_BUS_PUBLISH_PORT=4442 \
852-
-e SE_EVENT_BUS_SUBSCRIBE_PORT=4443 -e SE_START_XVFB=false --shm-size="2g" selenium/node-chrome:4.7.2-20221219
852+
-e SE_EVENT_BUS_SUBSCRIBE_PORT=4443 -e START_XVFB=false --shm-size="2g" selenium/node-chrome:4.7.2-20221219
853853
```
854854

855855
For more information, see this GitHub [issue](https://github.com/SeleniumHQ/docker-selenium/issues/567).
@@ -1204,7 +1204,7 @@ or
12041204

12051205
`Message: unknown error: Chrome failed to start: exited abnormally`
12061206

1207-
The reason _might_ be that you've set the `SE_START_XVFB` environment variable to "false", but forgot to
1207+
The reason _might_ be that you've set the `START_XVFB` environment variable to "false", but forgot to
12081208
actually run Firefox, Chrome or Edge in headless mode.
12091209

12101210
### Mounting volumes to retrieve downloaded files

0 commit comments

Comments
 (0)