-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Crash in Drake Visualizer in a docker #13639
Comments
Thank you for the report. Unfortunately, this is not a configuration that we test, and we have had discussions about whether we can even support drake-visualizer running in a Docker container on a wide enough variety of platforms. I will certainly take a look at the core dump, but the resolution may be an update to our documentation (in #13539) clarifying that this configuration is not supported. What is your host operating system and what graphics card and driver are you using? |
Fair enough. I can appreciate supporting the myriad of graphics drivers on the host is complex enough. I'm on Ubuntu 18.04 with a nvidia-440 driver. Graphics card is Quadro P2000 Mobile |
@cjds When you have a spare moment, can you try |
On prebuilt Docker images, rename `drake-visualizer` to `drake-visualizer.image`. Create a `drake-visualizer` script that prints a warning message with a pointer to the renamed file. Resolves RobotLocomotion#12483 and RobotLocomotion#13639
Closed by #13764. |
I'm getting a segmentation fault while trying to run the Drake Visualizer from a Dockerfile. This is a relevant dockerfile that replicates the issue
This is the run command
This is a Core dump
https://filebin.net/95fkjojxarojcfbe
The text was updated successfully, but these errors were encountered: