From b6d5b1efcf010ffff919dbdc9ebf56acf9ce72bd Mon Sep 17 00:00:00 2001 From: "Marvin A. Ruder" Date: Tue, 3 Jan 2023 04:27:20 +0100 Subject: [PATCH] Fix environment variable naming in README (#1761) --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 019f10464..a53bb53b8 100644 --- a/README.md +++ b/README.md @@ -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