You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-n NUM --server-num=NUM server number to use (default: 99)
-s ARGS --server-args=ARGS arguments (other than server number and
"-nolisten tcp") to pass to the Xvfb server
(default: "-screen 0 640x480x8")
Therefore, adding the DISPLAY into --server-args is incorrect. If I create a container and override the DISPLAY environment variable, xvfb won't start.
In my use case I am putting the hub and nodes in the same network, so using the same DISPLAY isn't working. The current containers work because DISPLAY=:99.0 which is the default for xvfb-run.
The text was updated successfully, but these errors were encountered:
double16
added a commit
to double16/docker-selenium
that referenced
this issue
Mar 22, 2016
- Add a common place for functions to be used in entry_point.sh
scripts.
- Refactor the calls to "echo $DISPLAY | sed..." into a function
named get_server_num.
- Add tests for this function.
- Fix regex used in sed call.
The current use of
xvfb-run
with respect toDISPLAY
is:The applicable documentation for
xvfb-run
is:Therefore, adding the
DISPLAY
into--server-args
is incorrect. If I create a container and override theDISPLAY
environment variable,xvfb
won't start.In my use case I am putting the hub and nodes in the same network, so using the same
DISPLAY
isn't working. The current containers work becauseDISPLAY=:99.0
which is the default forxvfb-run
.The text was updated successfully, but these errors were encountered: