ImportError: libGL.so.1: cannot open shared object file: No such file or directory about inference

[PawelPeczek-Roboflow]

I've taken a look and not found an elegant solution for the problem. The PR opened by @hvaria suggest switch to headless opencv for CLI completely. The problems are the following:

• there are installations where we resolve both cli requirements and core lib requirements - in presence of both, without libGL.so.1 being provided - even if there is no cv2.imshow(...) invocation - we have error - which would be the case in @yeldarby example (all libs installed) even with the change
• CLI uses visualisation (inference infer command) - so we cannot completely eliminate standard OpenCV

We could probably do the following (tradeoffs, pros and cons that I see outlined)

• have headless as a base requirement and have [desktop] extras in all libs and install standard cv on clients wish. Drawbacks:
  • people usually by default would try our lib in GUI-env - and would probably even use cv.imshow(...) to visualise, so asking them for additional effort may degenerate developer-experience
• catching the error would be possible - may be not necessarily elegant, but could work. The core of that problem is not the fact that one cannot install standard CV without GUI - it's rather the fact of additional shared libs being required - so I am leaning towards that approach, if we cannot apply the next option
• it seems that this problem could be completely avoided - and probably that should be done. If you analyse the series of imports leading to this error - you will discover that in inference_cli.lib.utils we import opencv through supervision (btw - it's headless by default and drags this into dependencies we install with inference) which is only used there due to read_yaml_file(...) util - which can be re-implemented or import could be pushed to another module. In long run - we shall think of developing CLI modules to be more command-oriented - to isolate potential domains of errors

[hvaria]

I fully agree with your analysis and the outlined approach to navigate these complexities.