Non-working web app using up-to-date Azure quickstart guide

[rieck-srlabs]

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

1. Follow the official steps on Microsoft's website to deploy the example Python3.9-based web app.

Any log messages given by the failure

Local build and deployment works, however, the site is not accessible. The reason is a Flask dependency issue as documented here.

Expected/desired behavior

Web app accessible.

OS and Version?

Linux deployment on Azure app services

Versions

Python3.9

Mention any other details that might be useful

There are already multiple PRs attempting to fix this issue:

• Update requirements.txt to fix broken tutorial #33
• Modified Flask version in requirement.txt for solving dependency conflict #32
• Update requirements.txt #24

---

Thanks! We'll be in touch soon.

[timgrossmann]

Really sad to see people actively contributing without microsoft merging PRs for their own documentation.
Spent nearly an hour trying to figure out what's wrong with my Azure Setup because I obviously thought the official Tutorials would work 😄

[ccg]

Y'all think this is ever going to get fixed? I'm trying to do my first Python/Docker deployment to Azure, so I followed the tutorial, not realizing that the tutorial does not work.

2025-01-26T17:36:16.116Z - Updating submodules.
2025-01-26T17:36:17.203Z - Preparing deployment for commit id '2c9481b8-6'.
2025-01-26T17:36:17.375Z - PreDeployment: context.CleanOutputPath False
2025-01-26T17:36:17.439Z - PreDeployment: context.OutputPath /home/site/wwwroot
2025-01-26T17:36:17.554Z - Repository path is /tmp/zipdeploy/extracted
2025-01-26T17:36:17.624Z - Running oryx build...
2025-01-26T17:36:17.629Z - Command: oryx build /tmp/zipdeploy/extracted -o /home/site/wwwroot --platform python --platform-version 3.9 -p virtualenv_name=antenv --log-file /tmp/build-debug.log  -i /tmp/8dd3e2ff05433ef --compress-destination-dir | tee /tmp/oryx-build.log
2025-01-26T17:36:21.939Z - Operation performed by Microsoft Oryx, https://github.com/Microsoft/Oryx
2025-01-26T17:36:22.022Z - You can report issues at https://github.com/Microsoft/Oryx/issues
2025-01-26T17:36:22.167Z - Oryx Version: 0.2.20250107.1+ef3fb2f9c490a4fbb1f76b5746cd4ba2ff0409f4, Commit: ef3fb2f9c490a4fbb1f76b5746cd4ba2ff0409f4, ReleaseTagName: 20250107.1
2025-01-26T17:36:22.263Z - Build Operation ID: fddda8315a0f9220
2025-01-26T17:36:22.310Z - Repository Commit : 2c9481b8-6939-4523-adcf-b1dc353b9600
2025-01-26T17:36:22.379Z - OS Type           : buster
2025-01-26T17:36:22.456Z - Image Type        : githubactions
2025-01-26T17:36:22.576Z - Detecting platforms...
2025-01-26T17:36:22.710Z - Could not detect any platform in the source directory.
2025-01-26T17:36:22.883Z - Error: Couldn't detect a version for the platform 'python' in the repo.
2025-01-26T17:36:24.345Z - Error: Couldn't detect a version for the platform 'python' in the repo.\n/bin/bash -c "oryx build /tmp/zipdeploy/extracted -o /home/site/wwwroot --platform python --platform-version 3.9 -p virtualenv_name=antenv --log-file /tmp/build-debug.log  -i /tmp/8dd3e2ff05433ef --compress-destination-dir | tee /tmp/oryx-build.log ; exit $PIPESTATUS "
2025-01-26T17:36:24.687Z - Generating summary of Oryx build
2025-01-26T17:36:24.864Z - Parsing the build logs
2025-01-26T17:36:24.956Z - Found 0 issue(s)
2025-01-26T17:36:25.095Z - Build Summary :
2025-01-26T17:36:25.289Z - ===============
2025-01-26T17:36:25.373Z - Errors (0)
2025-01-26T17:36:25.490Z - Warnings (0)
2025-01-26T17:36:26.007Z - Deployment Failed. deployer = ms-azuretools-vscode deploymentPath = ZipDeploy. Extract zip. Remote build.

I also tried to follow the Azure App Service tutorial for Python and Flask, but it also resulted in a broken deployment -- looking at the logs, I could see that it was crashing and rebooting every 5 seconds with some other Oryx-related error messages.