Closed renhaofan closed 2 years ago
Thanks for the feedback. I'll check it and let you know.
Hallo @renhaofan,
I can confirm that the command vglrun -d :2 glmark2
(and also vglrun -d :1 glmark2
) does not work correctly. It opens the rendering window and it closes it immediatelly. Unfortunately I cannot explain the reason.
However, I don't find such an example on the page you've mentioned above.
There is only the command vglrun glmark2
, which works correctly independently of the display number.
Regards, accetto
Hallo @renhaofan,
I can confirm that the command
vglrun -d :2 glmark2
(and alsovglrun -d :1 glmark2
) does not work correctly. It opens the rendering window and it closes it immediatelly. Unfortunately I cannot explain the reason.However, I don't find such an example on the page you've mentioned above.
There is only the command
vglrun glmark2
, which works correctly independently of the display number.Regards, accetto
Thanks for your quick response. I have tried some docker images with virtualGL, but all failed. From your repo, I realize myebe that because ${DISPLAY}
and QT_X11_NO_MITSHM
. Next week, I will try to solve this problem. If I solved that, I will let you know. Anyway, thanks a lot.
You're welcome.
I hope you've found that you can override the VNC/noVNC parameters, including the display number, using an external file. It can simplify experimenting. Check the part At VNC/noVNC startup-time in this Readme file.
You're welcome.
I hope you've found that you can override the VNC/noVNC parameters, including the display number, using an external file. It can simplify experimenting. Check the part At VNC/noVNC startup-time in this Readme file.
Yes. Before I created the issue, I have noticed that and test. Thanks for you remind.
FYI: I've just updated the images on Docker Hub. There is a newer VirtualGL 3.0.1. Maybe it will help.
FYI: I've just updated the images on Docker Hub. There is a newer VirtualGL 3.0.1. Maybe it will help.
I will try that later and let you know if successful.
By the way, I use this docker image to solve the VirtualGL problem, which is based on the nomachine with VirtualGL naturely. And I noticed you comment the nomachine in your Dockerfile. I hope that docker image is helpful for you.
Closing because of no further actions from the requester.
I do not have the appropriate hardware to develop the subject at the moment.
I met the same problem as described in Container doesn't start with volume .X11-unix:rw. I follow your advice, manually change the
DISPLAY
:After that, I run the command
vglrun glmark2
, no correspondence.Then I run the command
vglrun -d :2 glmark2
, but error occurred like below:However,
vglrun -d :2 glxgears
look like good, and no error reported, but it's slower: