Package deployment fails on v3.0.0

[barinalex]

With the update to v3 deployment started to fail with:

Run azure/webapps-deploy@v3
Package deployment using OneDeploy initiated.
Error: Failed to deploy web package to App Service.
Error: Deployment Failed, Error: Failed to deploy web package using OneDeploy to App Service.
Not Found (CODE: [40](https://github.com/pure-fa/fa-cbs-lighthouse/actions/runs/6532560651/job/17735980172?pr=85#step:16:41)4)

On v2 the workflow and function app configuration we have was working. Since the release doc explicitly says that Users who are currently using the webapps-deploy@v2 can still use the same action without any change in the workflow file. I assume no changes are needed on our side.

Our workflow for reference:

    - name: Publish package
      id: publish_package
      uses: azure/webapps-deploy@v3
      with:
        resource-group-name: ${{ env.AZURE_FUNCTION_RESOURCE_GROUP_NAME }}
        app-name: ${{ env.AZURE_FUNCTION_APP_NAME }}
        package: ${{ env.AZURE_FUNCTION_APP_PACKAGE_PATH }}

[tschirky]

I have the same issue with v3 (v2 works). When digging into the AppServicePlatformLogs, I can find the following logs:

EventName:ContainerStopped - Reason: - Message: - ContainerIDs:4c98f9dc3faec6fc00a299e9acdd5870c9bc483076471716353dacc837f5f4e7 - AdditionalInfo:
Stopping site <app-name> because it exceeded memory limits.

[dannysongg]

Thanks for bring this to our attention @barinalex. Are you trying to deploy to a consumption (serverless) function app?

[tschirky]

@dannysongg We're using a consumption plan, yes.

[sgollapudi77]

Hey @tschirky , @barinalex if you're deploying the Function apps, did you try using this action.

[tschirky]

@sgollapudi77 No we haven't. What's the rational behind using the "functions-action" and not the "webapp-deploy" action? I'm a bit confused, as we're having a web app on app services, and not a pure function app.

[github-actions[bot]]

This issue is idle because it has been open for 14 days with no activity.

[gopher194]

Hi, I was testing v3, but can't make it work:

• replaced:

• name: Deploy APP uses: azure/webapps-deploy@v2 with: app-name: ${{ env.AZ_APP_NAME }} package: app-artifact

  That deploys successfully, with:

• name: Deploy APP uses: azure/webapps-deploy@v3 with: app-name: ${{ env.AZ_APP_NAME }} package: app-artifact type: ZIP clean: false restart: true

  that lamentably fails with this error:

  Run azure/webapps-deploy@v3 Package deployment using OneDeploy initiated. node:events:491 throw er; // Unhandled 'error' event ^

Error: EISDIR: illegal operation on a directory, read Emitted 'error' event on ReadStream instance at: at emitErrorNT (node:internal/streams/destroy:157:8) at emitErrorCloseNT (node:internal/streams/destroy:122:3) at processTicksAndRejections (node:internal/process/task_queues:83:21) { errno: -21, code: 'EISDIR', syscall: 'read' }

[dannysongg]

@gopher194 I will need the name of your app to look into this. If you do not want to post it here, please email me at dannysong@microsoft.com.

[github-actions[bot]]

This issue is idle because it has been open for 14 days with no activity.

[jwhazel]

@gopher194 and anyone else having the same problem with the EISDIR error and happens to land here: the issue seems to be from setting package to point to a directory instead of a file. This fixed it for me:

    package: *.zip
    type: ZIP

Suggestion for Azure team: make the reason for this error a little more verbose.

[github-actions[bot]]

This issue is idle because it has been open for 14 days with no activity.

[kobe-patrickandrade]

The issue is still happening

[martijnvanderpol]

The issue is still happening

I forgot to add WEBSITE_RUN_FROM_PACKAGE with the value 1 to the App Settings of my Web App. This tells Azure that you want the app service to run from the package (no kidding, Sherlock haha) you’ve provided. So, maybe this is the same issue for you and others encountering it! 🤞🏻