Kudu vs. Kudu Lite

Question

I am migrating a PHP workload. I have a single Linux app service plan. One of my web-apps deploys perfectly on every push to GitHub. Two other web-apps fail on deployment. When I go to the deployment tools for the one that works, I see this: Kudu but the one that doesn't work I get Kudu Lite.

The deploy log for Kudu looks like:

TIME ACTIVITY LOG
1:31:54 PM Updating submodules.
1:31:54 PM Preparing deployment for commit id '8d32c96aa5'.
1:31:54 PM Running custom deployment command...
1:31:54 PM Not setting execute permissions for bash deploy.sh
1:31:54 PM Running deployment command...
1:31:57 PM Running post deployment command(s)...
1:31:57 PM Triggering recycle (preview mode disabled).
1:31:57 PM Deployment successful.

The deploy log for the Kudu Lite:

7:42:15 AM GMT-5 Failed temp-59 (N/A) Fetch from git@github.com:xxxxx/xxxxx.git

Clicking on Show Logs... shows:

error: cannot run ssh: No such file or directory\nfatal: unable to fork\n\n/usr/bin/git fetch origin --progress

Is there a way to force the deployment through Kudu vs. Kudu Lite? Is there a way to get Kudu Lite to deploy a simple PHP site on a Linux Web App?

Thanks!!!

Answer 1

I received a recommendation to make an appConfig setting:

SCM_ENABLE_DYNAMIC_INSTALL = false

Since setting this, I have been able to push to my GitHub repository and the deploy not fail.