Run Selenium Grid in kubernetes: unable to open display "selenium-node-chrome:99"

[audrey h]

 i tried to use the selenium/video:ffmpeg-4.3.1-20230221 in kubernete to record the videos, when i log in to the ffmpeg container, i seems not able to open the displayxset -display selenium-node-chrome:99 b off
xset:  unable to open display “selenium-node-chrome:99”any idea on this ? attached my yaml files for the chrome/chrome service/video

Video log shows below:

2023-03-06 22:25:55,700 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.

2023-03-06 22:25:55,703 INFO supervisord started with pid 7

2023-03-06 22:25:56,706 INFO spawned: 'video-recording' with pid 9

2023-03-06 22:25:56,709 INFO spawned: 'video-ready' with pid 10

Checking if the display is open...

2023-03-06 22:25:57,712 INFO success: video-recording entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2023-03-06 22:25:57,712 INFO success: video-ready entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

Waiting before next display check...

Chrome node is working ok:

22:02:32.715 INFO [NodeServer.execute] - Started Selenium node 4.8.1 (revision 8ebccac989): http://selenium-node-chrome:5555

22:02:32.826 INFO [NodeServer$1.lambda$start$1] - Sending registration event...

22:02:33.538 INFO [NodeServer.lambda$createHandlers$2] - Node has been added

[Serguei Kouzmine]

it apppears
the image  selenium/node-chrome does not have X windows

see 

https://github.com/SeleniumHQ/docker-selenium/blob/trunk/Base/Dockerfile

 so you have to be running headless