Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
7,630 questions
After scaling up from S1 to P0v3 in Azure Web App Service, deployment errors occur
![](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(217.60000000000002, 84%, 31%)' 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)
주원 김
0
Reputation points
After scaling up from Standard S1 to Premium P0v3 in Azure Web App Service, I encountered a deployment error. The deployment logs showed the message "ERROR - multi-container unit was not started successfully." I've tried various solutions such as modifying the WEBSITES_CONTAINER_START_TIME_LIMIT and port numbers, but the issue persists. It's strange because the same environment variables and Dockerfile settings were working fine in Standard S1, but not in Premium P0v3. What could be the problem?
{count} votes
-
![](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(185.6, 59%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
SnehaAgrawal-MSFT 21,266 Reputation points2024-02-28T14:56:41.9533333+00:00 @주원 김 Thanks for reaching here! Could you please access logs to narrow down the issue. Note that the Multi-container is currently in preview. There are limitations on App Service platform features are not supported: Check this doc link- https://learn.microsoft.com/en-us/azure/app-service/configure-custom-container?tabs=debian&pivots=container-linux#preview-limitations Please let us know.
-
주원 김 0 Reputation points
2024-02-29T00:22:21.1066667+00:00 I've also checked this document. The part that I really don't understand is that I applied the same Docker Compose settings to both Standard S1 and Premium P0v3, but only P0v3 is experiencing an error. I can check the deployment log, but there are no other reasons or error logs printed except for the message 'ERROR - multi-container unit was not started successfully
-
SnehaAgrawal-MSFT 21,266 Reputation points
2024-02-29T09:18:50.5666667+00:00 @주원 김 Reached you internally, as this need more information.
-
주원 김 0 Reputation points
2024-03-06T00:31:14.3066667+00:00 I have sent an email but have not received a reply yet
Sign in to comment
Sign in to answer