Hi ​@saitejajampula, welcome to the team!

You’re already using --no-display in your inference server command, which is right—this flag should prevent the inference server from opening any visual output, and works well in headless setups.

However, I wonder if the ROS2 node (video_infer) might still be triggering some OpenGL or pyglet-related functionality? I’m not sure I’ve seen anyone working with Metis and Voyager on ROS or ROS2, although it’s a really exciting idea!

So in this case, the inference server is probably behaving correctly, but perhaps the client may not be fully headless-compatible by default? Maybe that’s something we can look into between us?

Hi ​@Spanner ,

Thank you for the warm welcome and your helpful insights!

You're absolutely right — the inference server is functioning correctly with the --no-display flag, and I can confirm that no visual output is being attempted from the server side.

However, as you suspected, the video_infer_node in ROS 2 does appear to be triggering some GUI-related functionality, likely via pyglet, which is resulting in the warning:

       pyglet could not access the display, OpenGL is not available: No standard config is available.

Despite this warning, the node is able to read video frames, process them, and publish inference results without issue. So it's not blocking functionality, but it’s something I’ll look into cleaning up for a fully headless deployment.

Thanks again for the support — this hybrid setup of ROS 2 and Metis is indeed experimental, but quite promising. I'm happy to share my results as things evolve!

Best regards,
Saiteja Jampula

Excellent work, thanks for the update ​@saitejajampula! Please do keep me posted on how it’s progressing - robotics is about the most exciting area of AI involvement right now, if you ask me!

Sounds like you’re working on something very cool. What’s the project?

Hi ​@saitejajampula,

Just as a heads up, it is a known issue that the warning

> pyglet could not access the display, OpenGL is not available: No standard config is available.

will appear whenever you run on a system which doesn’t have working OpenGL, regardless of whether you care about that or not. As such that warning doesn’t imply that pyglet/GL GUI calls are being made. That’s why you find that there is no issue despite the warning, as you’re not expecting to use GL anyway.

We are working on suppressing this warning so it only appears if you are expecting OpenGL to work to avoid confusion like this. Unfortunately due to the way this bit of the code is written it is somewhat harder than it sounds :)

Ah, that’s interesting to know, thanks George! It’s reassuring to know that it’s not actually impacting operation in the meantime. Thanks bro!