-
Notifications
You must be signed in to change notification settings - Fork 118
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
Durable Functions Memory Issues After Isolated #1173
Comments
Ok I definitely think something was introduced. I changed my dockerfile to point at the old version and memory issues went away. No error message or issues, everything runs fine. New dockerfile:
@pragnagopa I think this might be worth looking into. Im willing to share my findings and help out how I can but I think there is an issue here somewhere. |
@unfixa1 Docker does support running x86-64 binaries natively via Rosetta. I also moved to Orbstack and the problem persisted there, just to rule out that it could be Docker Desktop. I will test on an intel system at some point today. Downgrading to 4.35 is the only thing that will not cause the application to crash. |
I was able to run the project on a windows intel-based system no problem. Debugging further into this issue is out of my level of expertise but what I know is that after the 4.36 update I cannot run a durable function app via a docker image on an m-series machine where I was able to before this update. We will move forward with just reverting to the old version for now and hopefully a future update can remedy this issue. |
@brandonwatts We have also been seeing the same problem since the update to 4.36, also running on Mac M-Series. And the workaround is the same, to stay on 4.35 until this is fixed. |
Hello, I was wondering if someone could help me on some issues I am running into. We have a durable python function app that we have been running via a docker image for a long time now and everything has worked great. Recently after returning to the application we are not able to run it locally anymore. The application will start up and then fail due to memory issues. After some digging I think it may have been this PR that caused the issues. Im not certain but its my best guess. I thought it was just a local issue but my entire team is running into the same issue. We are all on M-Series Mac if that plays any role. Below are some of the issues. The application runs fine locally as in func start. This issue is isolated to just when running in the docker container.
Docker Engine v.27.2.0
azure-functions-durable==1.2.9
azure-functions==1.19.0
dockerfile:
The text was updated successfully, but these errors were encountered: