Running coreWCF in Azure App Service Linux does not work

Anita A 75 Reputation points

When deploying coreWCF to Linux App Service I get this error: "Container <container-name> for site <site-name> did not start within expected time limit. Elapsed time = 230.9697425 sec".

Can you please clarify these things:

  • Can the coreWCF be deployed to Linux App Service?
  • When deployed to App Service does the coreWCF run on IIS or on Kestrel?


Microsoft Technologies based on the .NET software framework.
2,303 questions
Windows Communication Foundation
Windows Communication Foundation
A Microsoft runtime and set of application programming interfaces in the .NET Framework for building service-oriented applications.
297 questions
Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
6,033 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. brtrach-MSFT 11,936 Reputation points Microsoft Employee

    @Anita A Yes, CoreWCF can be deployed to Azure App Service. When using an Linux web app, it will run on Kestrel.

    However, there are a few things to note:

    1. Azure App Service does not support NetTcpBinding. If you’re using NetTcpBinding in your WCF service, you’ll need to switch to using named pipes instead.
    2. When deploying CoreWCF to Azure App Service, the service is not hosted on IIS but on Kestrel. This is because by default, the ASP.NET hosting runs the process using the Kestrel web server.
    3. If you’re encountering issues with the container not starting within the expected time limit, it could be due to a variety of reasons such as application startup time, application errors, Dockerfile issues, etc. You might want to check the logs for more detailed error messages.
      1. To check the deployment logs for your container go to:
        1. In the Azure Portal, select your web app.
          1. Go to deployment center
            1. select the "logs" header
              1. From here you can see your deployment logs, which will provide you with a more detailed error of what is going on.