Docker quickstart RQD error about opencue HOT 2 OPEN

Hi @Tilix4, I ran RQD via docker and came across a similar set of errors.

It seems like there is a limitation with the pynput module when running in a docker container as it requires an X11 server for the GUI. It's detailed in this doc.
Hence why it didn't work even after you manually installed it.
I've created a fix and sent a PR which will be referenced below.

However, this does not have an effect over RQD being unable to connect to CueBot over gRPC.
I still got the same GRPC connection failed issue with CueBot simply running locally via the IntellIJ IDE even after the pynput fix.

from opencue.

A couple of things to note here:

• There does appear to be an issue with pynput, but it shouldn't prevent RQD from starting up.
  • A fix is in progress and I've commented on #1311.
  • If Nimby is not able to start, RQD should just essentially deactivate it -- per the Using Nimby nop messages it looks like that's working here.
• When you're using the quickstart's sandbox setup, some RQD connection errors are expected.
  • The way our Docker compose setup works is to start all containers at the same time. Most of these containers will need to wait for another component's container to be up and running in order to start properly. What you're seeing here is the RQD container has started but the Cuebot container isn't up and running yet, so RQD throws an error then waits a while before it retries.
  • Based on the output in your second screenshot, RQD startup did succeed after Cuebot finished starting up.

Prior to you installing pynput, I would have expected the same -- that RQD would finish starting up eventually despite the error. Is it possible for you to check this again with a fresh setup?

Maybe a "Known Issues" section on the quickstart doc page would help clarify some of these things.

from opencue.