This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(176, 70%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETM%3C/text%3E%3C/svg%3E)
We are trying to deploy a geodjango project on Azure App Service. However, the required geospatial dependencies are not yet available for Oryx on the App Service at this time.
The issue has been patched with Oryx release exp-20210721.2 (https://github.com/microsoft/Oryx/releases/tag/exp-20210721.2), but currently the Azure App Service runs Oryx Version: 0.2.20210605.4 to build the application.
When will Oryx exp-20210721.2 or newer be available on the App Service?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 92%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
@Timothy Mans , Thanks for the question. We're checking on this internally and will get back to you shortly. Thanks for your patience.
Apologies for delay in getting back on this, I was waiting to hear from the team.
On my test WebApp I see 0.2.20210826.1 Oryx version.
Just checking, how exactly are you deploying the code or just setting up before the deployment? Kindly share some more details about your scenario.
To receive updates on runtimes and versions supported by Oryx and App Service, you may always subscribe to Azure Updates or watch the github.com/Azure/app-service-announcements tracker.
Just to highlight:
the Oryx includes two command-line applications; the first is included in the build image and generates a build script by analyzing a codebase.
The second is included in run images and generates a startup script. Both are aliased and accessible as oryx in their respective images.
Legacy stack detection can be enabled by using the App Setting ENABLE_ORYX_BUILD=false
Kindly let us know, I'll follow-up/share more updates here. Thanks again for your patience.
Thanks for the response.
Oryx gets activated by a azure/webapps-deploy@v2 call in the workflow (YAML file) which is triggered "on commit" through GitHub actions: 
25839862, Firstly, apologies for the delayed response on this from over the weekend. I'm following with you privately for some additional details.
To benefit the community, posting our offline conversation.
App Service roll out was complete across all the regions. 25839862 confirmed - "Oryx has been updated on the app service to the 0826 version for us in the Western Europe region."
Thanks for your update @Timothy Mans and collaboration.