Publishing Azure Linux Web App does not update the running application

[microsoft]

Publishing Azure Linux Web App does not update the running application

[kichalla]

@valeriob AppService team now supports 'running from package' which is supposed to fix issues like this. Could you try with this and let us know if you are still seeing this issue?
https://docs.microsoft.com/bs-latn-ba/azure/app-service/deploy-run-package

[valeriob]

Hi,
we are using octopus deploy at the moment.
https://octopus.com/docs/deployment-examples/azure-deployments/deploying-a-package-to-an-azure-web-app

[gpcastro]

Thanks for reaching out. We're aware of this issue and we're working on a fix. In the meantime, have you tried using slots?
They allow you to update your web app without conflicting with files being used by the version currently running.

[valeriob]

Hi,
glad to hear you are working on it, I've tried slots but they add a little bit of complexity to our deployment. I look forward for an updated.
Thanks !

[bharatdwarkani]

Any update on this when it is going to be fixed?

[ClientIco]

Also would like to know ?

[kichalla]

Are you still able to reproduce this issue?

[valeriob]

Hi,
i just tested a few times, yes it still require a manual restart to work.

[shotyme]

This issue occurs in the Linux based Azure Functions as well.
Can somebody help me please?

Edit: If someone is facing the same issue. The workaround for linux azure functions is: stop the function, start the function, re-deploy the code

[paulbatum]

File locking issues are common on .NET Core because it does not have the shadow copying behavior that was present on .NET Framework. There are two common approaches to this problem:

1. Modifying the publish profile to take the app offline during deployment. The setting is called EnableMSDeployAppOffline. I know this setting works when deploying Azure Functions, but I haven't tried it for a linux web app.
2. Deploy using Run From Package (app service documentation here, functions documentation here). This approach should work in all scenarios.

[arroyc]

please feel free to reopen this issue if you are experiencing it

[valeriob]

Pls do not close it, we still have this problem.
Thanks

[valeriob]

thanks @kichalla, i will try this feature, but it will drastically change our automated deployment pipeline, last time i tried az cli was a nightmare to script due to escape problems Azure/azure-cli#7874

[kichalla]

but it will drastically change our automated deployment pipeline, last time i tried az cli was a nightmare to script due to escape problems Azure/azure-cli#7874

How are you deploying your app to AppService? by zip deploying already built bits or zip deploying and making the build to happen on app serivce or pushing your repo? more details will help us narrow the problem.

This run from package feature is just an appsetting so not sure what you meant by script

[kichalla]

Gentle ping.

[schauhan232]

Hi,
we are using octopus deploy at the moment.
https://octopus.com/docs/deployment-examples/azure-deployments/deploying-a-package-to-an-azure-web-app

Did you find any solution, we are using same and I have been facing same issue.

[valeriob]

You can use deployment slots or just restart the WebAp with a script

$webAppName = '#{Octopus.Action.Azure.WebAppName}'
$rg =(Get-AzureRmWebApp -Name $webAppName).ResourceGroup
Restart-AzureRmWebApp -Name $webAppName -ResourceGroup $rg