Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

xvfb-run is being used incorrectly to set DISPLAY #184

Closed
double16 opened this issue Mar 22, 2016 · 1 comment
Closed

xvfb-run is being used incorrectly to set DISPLAY #184

double16 opened this issue Mar 22, 2016 · 1 comment

Comments

@double16
Copy link
Contributor

The current use of xvfb-run with respect to DISPLAY is:

xvfb-run --server-args="$DISPLAY -screen 0 $GEOMETRY -ac +extension RANDR" \

The applicable documentation for xvfb-run is:

-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.

@double16
Copy link
Contributor Author

Clarification... xvfb starts but the browser cannot start if DISPLAY is other than :99.0

gundal referenced this issue Apr 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.
@lock lock bot locked and limited conversation to collaborators Aug 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant