opencv-contrib-python-headless as requirement

[maxstrobel]

System information (Please provide as much relevant information as possible)

• MediaPipe Solution (you are using): Python wheel
• Programming language : Python
• Are you willing to contribute it (Yes/No): Yes

Describe the feature and the current behavior/state:

Currently opencv-contrib-python is installed as requirement. If you want to use mediapipe inside a Docker container huge images are required, because of GUI dependencies.

Proposal: Use opencv-contrib-python-headless as requirement, which is slimmer & works without the heavy dependencies.

Will this change the current api? How?

No.

Who will benefit with this feature?

Python users that develop / deploy inside Docker containers.

Please specify the use cases for this feature:

Development / deployment of the Python mediapipe package inside Docker containers.

Any Other info:

[kuaashish]

Hi @maxstrobel, Could you please provide the steps to reproduce and more information about the issue. Thank you

[google-ml-butler]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you.

[google-ml-butler]

Closing as stale. Please reopen if you'd like to work on this further.

[gentnm]

@kuaashish I just ran into the same problem. I can provide some steps to reproduce the issue and give some further information.

mediapipe currently has opencv-python-contrib as a dependency which starting with version 4.3.0.38 is not working in headless environments anymore (cf. opencv/opencv-python#370) . So in a docker setup, mediapipe won't be working anymore.

Therefore it would be nice to either use the headless version in all cases or to also be able to specify a headless version for mediapipe.

Build a docker image with

FROM python:3.9-slim
RUN pip install mediapipe

ENTRYPOINT [ "python" , "-c"]
CMD [ "import mediapipe" ]

and then execute:
docker build -t mediapipe-test . && docker run mediapipe-test

[gentnm]

@kuaashish @sureshdagooglecom

Is it possible to reopen this or should I open a new issue?

[kuaashish]

Hi @gentnm, Please raise a new issue with mentioning the reference of this issue. Thank you!