Regional vnet integration not working with custom image(wildfly) deployed in azure app service.Although i have followed the Microsoft link for regional vnet integration.

Sandeep Kumar 1 Reputation point

I am currently working on an app that need wildfly server for deployment.I have created the Dockerfile for wildfly and build and push images to Azure Container Registry(ACR).When i simply deploy app in app service with docker image option then it works correctly and I can access all the web content but i need to connect container running in app service with regional VNET.I followed the Microsoft recommendation for Regional VNET integration doc .I have kept the PORT variable dynamic and SSH port variable to 2222 but .But when i tried to connect vnet with container container is being stopped with error "****Container** aa435621_0_39ed47c7 for site aiatestapp has exited, failing site start
2020-06-09T19:04:05.892Z ERROR - Container aa435621_0_39ed47c7 didn't respond to HTTP pings on port: 80, failing site start. See container logs for debugging.
2020-06-09T19:04:05.898Z INFO - Stopping site aa435621 because it failed during startup.**"

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
4,899 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Grmacjon-MSFT 10,086 Reputation points

    Hello @Sandeep Kumar ,

    Apologies for the late response and for the frustration this issue might have caused. Based on the error message, your container is not responding to HTTP pings on port 80. Can you please share with us the docker command you are using so we can see if your Dockerfile is exposed on port 80?

    You can use the EXPOSE instruction in your Dockerfile to expose port 80 or
    Use the WEBSITES_PORT app setting with a value of "80" to expose that port.

    Keep in mind ports other than 80 and 8080 are ignored based on this documentation.

    Please let us know if you have further question or if you are still seeing this error