-
Notifications
You must be signed in to change notification settings - Fork 264
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
Fortress and Garden on 20.04 NVIDIA VirtualGL Docker gets killed immediately after start, ogre2 is affected but not ogre #1746
Comments
Note: |
Looks like a duplicate of gazebosim/gz-rendering#526. If the goal is to run it in headless mode, have you tried setting the |
@azeey Yeah, it's possible, but my users want to run with a remote desktop from inside a Docker container, not just headless. I raised it because it works with Citadel + ogre2, and it's probably something that changed from the ogre2 version in Citadel to Fortress that made it wrong. So it might be able to get fixed. |
should be fixed by gazebosim/gz-rendering#794. Please re-open if issue persists |
Environment
dxdiag
and report the GPU-related information.system_profiler SPDisplaysDataType
. Copy the output here.~/.ignition/rendering
Description
gz sim shapes.sdf -v 4
orign gazebo shapes.sdf -v 4
, Gazebo gets killed right after the GUI is seen in ogre2, but ogre works correctly. Environment is Xvfb+VirtualGL 3.0.1 and Docker with NVIDIA 510.54. Works correctly in the exact same node using Xorg with NVIDIA drivers. Citadel also works correctly on ogre2.Steps to reproduce
gz sim shapes.sdf -v 4
orign gazebo shapes.sdf -v 4
Output
Hardware Info:
Fortress:
Garden:
ogre2.log Fortress:
ogre2.log Garden:
The text was updated successfully, but these errors were encountered: