-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make it possible to let mediapipe be installed in headless environments #3661
Comments
Ping |
I would suggest either
|
Bump I am also looking an elegant solution to containerize mediapipe and opencv to Python Docker image. |
Hello everyone, I'm trying to build a headless version of Mediapipe. This is the error I got.
|
Me too. Looking for headless installation of mediapipe (opencv-contrib-python-headless instead of opencv-contrib-python for underlying dep). |
is there any work around for this problem right now, or how people solve this problem |
I had to install apt-get update && \
apt-get install --no-install-recommends -y \
libegl1-mesa-dev \
libglib2.0-0 Not elegant solution at all. |
i changed the docker image to
i think it's working for me |
Hi! I think I've found the solution, I've written a gist for it: https://gist.github.com/FrankwaP/f45c9180cf85e5abe563d97f0af84ae5 Basically before installing Mediapipe, you install |
Please make sure that this is a feature request.
System information (Please provide as much relevant information as possible)
Official python docker image python:3.9-slim (Debian based)
Describe the feature and the current behavior/state:
Reopen from #3403
It would be great to be able to install mediapipe in a headless version.
Currently mediapipe in python depends on opencv-contrib-python which needs a lot of GUI components not needed in headless environments such as slimmed down docker containers. Due to this a lot of overhead is created for people using mediapipe in a streamlined environment without GUI interaction.
In order to make mediapipe run in headless environments, the opencv-contrib-python requirement could be swapped for opencv-python-headless .
I see three possible approaches for this:
Will this change the current api? How?
In the headless version, maybe some features need to be turned off. I am not familiar with the complete set of features of mediapipe, so I am not sure if GUI features from opencv-contrib-python are used anywhere.
For my usecase everything seems to work fine.
Who will benefit with this feature?
Anyone running mediapipe in headless environments.
Please specify the use cases for this feature:
Create a service to be deployed in a cloud setting that takes an image and processes it with mediapipe.
No GUI features needed there.
Any Other info:
Sample docker file to demonstrate current problem:
The text was updated successfully, but these errors were encountered: