-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
VNC server does not work in selenium/standalone-chrome-debug containers on hardended PaX kernels #205
Comments
Well, I found that this issues caused by Grsecurity/PaX on host machine (dmesg output is below):
And currently it is not clear how to run selenium-*-debug containers properly to solve this. |
docker pull elgalu/selenium:2.53.0h
docker run --rm -ti --name=grid -p 4444:24444 -p 5900:25900 \
-v /dev/shm:/dev/shm -e VNC_PASSWORD=hola elgalu/selenium:2.53.0h |
Sorry I just saw you already put some info on the previous comment, please only answer what's missing |
Perhaps I will just add |
BTW, I found workaround: just disable kernel.grsecurity.harden_ipc kernel parameter.
Also it can be added to /etc/sysctl.d. I do not like this solution but it works with current version of selenium/standalone-*-debug containers and help if want just debug some single issue in Selenium test. |
@elgalu I forgot to attach a full output you asked. It is below.
|
Steps:
$ docker run -P -it -p 5900:5900 selenium/standalone-chrome-debug
Output of x11vnc:
If I run (by hands) x11vnc with
sudo -u seluser
then all works OK and I can connect to it.The text was updated successfully, but these errors were encountered: