-
Notifications
You must be signed in to change notification settings - Fork 254
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
How do I use a different python version for prompt flow custom runtime? #154
Comments
We're looking to do something similar, you can use
It's ugly and probably prone to breakage so YMMV, but it works with the current image. If you want to investigate further, this is what helped me:
|
@stewartadam Thank you! I did the same thing by updating the conda env, but this idea of copying the promptflow-runtime wheel didn't occur to me. Good idea👍 BTW! For now we have decided to not go through this route! Thank you! |
Hi, is this issue expected to be fixed in the future? |
@ebotiab agreed, this should not be so hard to change base image Python version |
@stewartadam can you please also tell me how to adjust the liveness and readiness of the container, And what do you mean by that promptflow_runtime whl is not published. And, I have also taken reference from your suggestion, but at the end I got stuck on a point in the final deployment, below is the error I am facing: |
We are using our own environment definition to build the promptflow runtime image, and use it as the base for provisioning the custom runtime on AML compute instance for doing batch and evaluation runs.
So far we are good.
What we need is a way to use a different python version e.g. Python 3.11 on my custom runtime. Is there a way I can do this? So far what I have observed is all the base images supplied by mcr use python 3.9.
My docker file looks like this
FROM mcr.microsoft.com/azureml/promptflow/promptflow-runtime-stable:20240515.v1 COPY ./* ./ RUN pip install -r requirements.txt
Is there a way I can define something in my docker file to upgrade the python version?
The text was updated successfully, but these errors were encountered: