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(198.4, 2%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBP%3C/text%3E%3C/svg%3E)
I have a Python / Flask application that deploys to Azure without any errors in the logs. Unfortunately, the app does not appear after deployment. I only see the default app with UI that says 'Your web app is running and waiting for your content'.
I'm deploying the app using VS Code. I already went through the Troubleshooting guide but I'm not missing anything.
What seems to be causing the issue is that my app has a long list of packages in requirements.txt. I verified this causes a problem by testing the hypothesis using the 'msdocs-python-flask-webapp-quickstart' app.
I created a clean deployment of the test app and it deployed with no errors and the app appeared.
I then modified the test app by adding a list of imports into app.py and I added lines into requirements.txt to match all the packages I need for my own app.
When I then made a new clean deployment of the modified test app, it exhibited the same issue as my own app.
Simply adding a longer list of python packages causes something to go wrong in the deployment. It looks like the app files are not getting placed where they should be. The result is that the app UI does not show even though the deployment does not report any errors.
I noticed in the deployment logs that it takes a while for pip install and then compression to run. But the app files (and app UI) still don't appear after that process is done.
Any suggestions on how to deploy a Python web app that has requires a lot of packages?
For reference, here are the contents of my requirements.txt
altair==5.2.0
annotated-types==0.6.0
anyio==4.3.0
attrs==23.2.0
azure-ai-documentintelligence==1.0.0b1
azure-ai-formrecognizer==3.3.2
azure-common==1.1.28
azure-core==1.30.1
blinker==1.7.0
cachetools==5.3.3
certifi==2024.2.2
charset-normalizer==3.3.2
click==8.1.7
distro==1.9.0
faiss-cpu==1.8.0
filelock==3.13.1
Flask==3.0.3
Flask-SSE==1.0.0
fsspec==2024.2.0
gitdb==4.0.11
GitPython==3.1.42
gunicorn
h11==0.14.0
httpcore==1.0.4
httpx==0.27.0
huggingface-hub==0.21.4
idna==3.6
isodate==0.6.1
itsdangerous==2.1.2
Jinja2==3.1.3
joblib==1.3.2
jsonschema==4.21.1
jsonschema-specifications==2023.12.1
markdown-it-py==3.0.0
MarkupSafe==2.1.5
mdurl==0.1.2
mpmath==1.3.0
msrest==0.7.1
networkx==3.2.1
numpy==1.26.4
oauthlib==3.2.2
openai==1.14.0
packaging==23.2
pandas==2.2.1
pillow==10.2.0
protobuf==4.25.3
pyarrow==15.0.1
pydantic==2.6.4
pydantic_core==2.16.3
pydeck==0.8.1b0
Pygments==2.17.2
python-dateutil==2.9.0.post0
pytz==2024.1
PyYAML==6.0.1
redis==5.0.3
referencing==0.33.0
regex==2023.12.25
requests==2.31.0
requests-oauthlib==1.4.0
rich==13.7.1
rpds-py==0.18.0
safetensors==0.4.2
scikit-learn==1.4.1.post1
scipy==1.12.0
sentence-transformers==2.5.1
six==1.16.0
smmap==5.0.1
sniffio==1.3.1
streamlit==1.32.2
sympy==1.12
tenacity==8.2.3
termcolor==2.4.0
threadpoolctl==3.3.0
tokenizers==0.15.2
toml==0.10.2
toolz==0.12.1
torch==2.2.1
tornado==6.4
tqdm==4.66.2
transformers==4.38.2
typing_extensions==4.10.0
tzdata==2024.1
urllib3==2.2.1
Werkzeug==3.0.2
I discovered that if I set the environment variable WEBSITES_CONTAINER_START_TIME_LIMIT to a large enough value, the web app was able to start properly. The start needed to happen after all of the python packages got installed and after the compression step. It was taking about half an hour for that process to finish
![](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(147.20000000000002, 55.00000000000001%, 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)
@Buck, Patrick , Apologies for the delayed response.
Glad to know that the issue is resolved. thanks for the follow and update.
Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer -- it will benefit community members to find the answers quickly.
Scenario: Python/Flask application deployment to Azure App Service using VS Code with app having long list of packages in requirements.txt.
Issue: The application deploys without any errors in the logs, but the app does not appear after deployment. Instead, the default app with UI that says ‘Your web app is running and waiting for your content’.
Posting the answer/solution shared by @Buck, Patrick .
Resolution:
By default, if your container does not respond after 230 seconds, it will time out. (This time out can be increased by with the WEBSITES_CONTAINER_START_TIME_LIMIT app setting.) (up to a maximum of 1800).
Ref: Troubleshooting ‘Container didnt respond to HTTP pings on port, failing site start’
If the answer helped (pointed, you in the right direction) > please click Accept Answer - it will benefit community members to find the answers quickly.