search

pierrekilly / docker-ros-box

The dockerized ROS box with hardware accelerated X11 support
MIT License
37 stars 15 forks source link

i couldn't run the gazebo #5

Open fakca opened 5 years ago

fakca commented 5 years ago

melodic-dev@322ed4d3fe0c /home $ gazebo-9.0.0 libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 152 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 40 Current serial number in output stream: 41 [255]

chitianqilin commented 4 years ago

I can't run Gazebo either. The followings are the error :

libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast

Could anyone help with it?

KingBoomie commented 3 years ago

I had the same problem. It was due to docker-ros-box initializing software-renderer, which didn't work on my ubuntu20 nvidia machine for some reason. Used the tutorial from here to modify docker-ros-box a little and got things working. You can probably try my fork: https://github.com/KingBoomie/docker-ros-box

@pierrekilly I can't test right now if my changes break the normal usage of docker-ros-box, but if they don't, or if someone is interested making this work for both, I'd love it if my changes got upstreamed.

pierrekilly commented 3 years ago

I like your change @KingBoomie, maybe you can make a PR?

KingBoomie commented 3 years ago

Sorry for the late reply.

I got someone to test it for me on a different machine also running an nvidia GPU, but for some reason, your default repo worked for them, while my changes didn't. I am currently unsure what causes this (maybe what drivers you have installed locally? maybe some weirdness in the docker setup?), but it's clear that upstreaming the current version isn't an option. (since it breaks everyone who uses the default software renderer). I fear that the amount of changes needed to have one repo autoconfigure for both architectures leads to enough additional complexity that it's not worth it.

Hopefully my repo is useful to people who run into the same problem.