Running coreWCF in Azure App Service Linux does not work

Anita A 105

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?

Thanks!

1 answer

brtrach-MSFT 16,676 Reputation points Microsoft Employee

2023-11-21T17:58:33.0266667+00:00
@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:

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.

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.

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.

To check the deployment logs for your container go to:

In the Azure Portal, select your web app.

Go to deployment center

select the "logs" header

From here you can see your deployment logs, which will provide you with a more detailed error of what is going on.
Please sign in to rate this answer.
Anita A 105 Reputation points

2023-11-23T14:56:49.89+00:00

Thanks for the clarification brtrach-MSFT. I am using BasicHttpBinding.

When I deploy CoreWCF (by just using the default coreWCF template) to Windows App Service it works out of the box, but that same service deployed to Linux App Service (not containers) does not work (I get the error from above). I have expected, since .NET is a cross platform, to work out of the box there as well. Or there are still some things to be done for the service to work on Linux?

Thanks!

brtrach-MSFT 16,676 Reputation points Microsoft Employee

2023-11-28T01:27:09.8166667+00:00

Are you able to run the image on a local Linux machine? Just want to ensure this is related to Azure and not the image itself.

Anita A 105 Reputation points

2023-11-28T09:50:54.3733333+00:00

I've tried to run the service on local docker container and it works, what happens in the Linux App Service I do not know, not sure what image is used, since I am just selecting .NET runtime so expect things to be all set up for running the service in there.

brtrach-MSFT 16,676 Reputation points Microsoft Employee

2023-12-03T22:13:55.81+00:00

It seems like you’ve done a good job of troubleshooting the issue so far. Since the service works on a local Docker container, it suggests that the issue might be specific to the Azure App Service environment.

Items I would suggest checking next:

Try a different deployment method: You could try a different deployment method like run from package (to avoid resource locking), using FTP/S, or local git deployment.

Scale up the App Service Plan: Sometimes, the issue could be due to insufficient resources. You could try scaling up to the next higher tier and re-trigger your pipeline.

Check the App Settings: There could be some settings that need to be configured in the App Service. For instance, you could try setting WEBSITE_WEBDEPLOY_USE_SCM=false in the app settings for your site.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Running coreWCF in Azure App Service Linux does not work

1 answer

Your answer