Cannot deploy NodeJS app from private GitHub repo

Question

Cannot deploy NodeJS app from private GitHub repo

:0 1

I am trying to deploy a Node 14 LTS web app using Azure and Kudu connected to my GitHub account for my deployment. However, when trying to deploy, it says the deployment status is failed. This is the error it shows me in "Show Logs":

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

I found a related question (https://learn.microsoft.com/en-us/answers/questions/152131/appservice-linux-amp-php74-deploy-failed-use-githu.html) that says to set SCM_ENABLE_DYNAMIC_INSTALL=false in application settings. However, when I do that, I get the following error:

"Operation performed by Microsoft Oryx, https://github.com/Microsoft/Oryx
You can report issues at https://github.com/Microsoft/Oryx/issues
Oryx Version: 0.2.20200917.1, Commit: 59deb778658a124cb74ea8e2c8f39fa87abcc9d9, ReleaseTagName: 20200917.1
Build Operation ID: |ttXwtfbuZOo=.100e490f_
Repository Commit : 20109c2fa598b3d8445dceeb22d7083f6f08c3f9
Detecting platforms...
Error: Platform 'nodejs' version '14' is unsupported. Supported versions: 4.4.7, 4.5.0, 4.8.0, 6.2.2, 6.6.0, 6.9.3, 6.10.3, 6.11.0, 6.17.1, 8.0.0, 8.1.4, 8.2.1, 8.8.1, 8.9.4, 8.11.2, 8.12.0, 8.15.1, 8.17.0, 9.4.0, 10.1.0, 10.10.0, 10.14.2, 10.21.0, 10.22.0, 12.18.2, 12.18.3"

I have set my stack to be Node 14 during the creation of the web app, and it says Node 14 LTS in my Deployment Center settings, as well as my General Settings in Configuration.

If I try to deploy a public repository on my GitHub, it seems to work fine. I've had some various forms of success by deleting the deploy key and webhook in my GitHub repo settings, but I do not want to keep experimenting with that kind of approach. I was also able to find a successful workaround by setting SCM_DO_BUILD_DURING_DEPLOYMENT=false and a custom post-deployment script defined in SCM_POST_DEPLOYMENT_ACTIONS_PATH. However, this produces undesirable side-effects and is not viable as a long-term solution.

This seems to be an ongoing issue that multiple users have had - see here: https://twitter.com/AzureSupport/status/1324171128747761671.

Any non-convoluted solutions to this?

ajkuma 28,036 Reputation points Microsoft Employee Moderator

2020-11-30T12:38:47.24+00:00

@:0 , Thanks for posting this question. I'm reaching out to you privately to gather some more information and work with you offline. Apologies for any inconvenience with this issue.
To benefit the community, will post back the findings/outcome.
ajkuma 28,036 Reputation points Microsoft Employee Moderator

2020-12-03T13:37:09.257+00:00

@:0 , Just checking in if you have had a chance to see my previous responses (reached out you privately as well). Kindly let us know if you need further assistance on this, I'll follow-up with you.
meme 1 Reputation point

2020-12-25T19:33:21.16+00:00

any news about this? I have same issue in deploying node14 from github to kudo/azure
ajkuma 28,036 Reputation points Microsoft Employee Moderator

2020-12-28T18:48:02.737+00:00

meme-8208, Copying the answer/solution shared by 0-2838 (Thanks to 0-2838 for the update)

"In Configuration, added the following values:

SCM_DO_BUILD_DURING_DEPLOYMENT=false
SCM_ENABLE_DYNAMIC_INSTALL=false
SCM_POST_DEPLOYMENT_ACTIONS_PATH=PostDeploymentActions

In GitHub repo, added the following folder to the root: 'PostDeploymentActions'. Inside that folder, I added a start script 'start.cmd' with the following lines:

npm install
npm start
"

I'd reported this issue and similar issue was fixed for a few users by adding SCM_ENABLE_DYNAMIC_INSTALL=false application settings, kindly let me know if it works for you. Will follow-up with you further.
:0 1 Reputation point

2020-12-28T18:59:04.977+00:00

Hello, sorry I haven’t been able to respond, I ended up just using an Azure Virtual Machine instead to save the headache. However, I DO NOT recommend adding a PostDeploymentActions start script. This script will time out in the build actions, and the build status will fail. The script will also prevent any new updates from being deployed. You would also have to kill other node processes on the service, which could have unintended consequences.
ajkuma 28,036 Reputation points Microsoft Employee Moderator

2020-12-29T07:36:24.073+00:00

Thanks for the follow-up, 0-2838.

Apologies for any frustrating experiencing with this. I was hoping to connect with you to get to the root of the problem with your subscription details (privately). Kindly let me know if you need further assistance with this.
I worked on multiple similar issues and we were able to fix with just by adding this setting SCM_ENABLE_DYNAMIC_INSTALL=false.
I have shared this feedback with our product team. Once again sorry for any inconvenience!

1 answer

Your answer

ajkuma 28,036 Reputation points Microsoft Employee Moderator

2020-11-30T12:38:47.24+00:00

@:0 , Thanks for posting this question. I'm reaching out to you privately to gather some more information and work with you offline. Apologies for any inconvenience with this issue.
To benefit the community, will post back the findings/outcome.
ajkuma 28,036 Reputation points Microsoft Employee Moderator

2020-12-03T13:37:09.257+00:00

@:0 , Just checking in if you have had a chance to see my previous responses (reached out you privately as well). Kindly let us know if you need further assistance on this, I'll follow-up with you.
meme 1 Reputation point

2020-12-25T19:33:21.16+00:00

any news about this? I have same issue in deploying node14 from github to kudo/azure
ajkuma 28,036 Reputation points Microsoft Employee Moderator

2020-12-28T18:48:02.737+00:00

meme-8208, Copying the answer/solution shared by 0-2838 (Thanks to 0-2838 for the update)

"In Configuration, added the following values:

SCM_DO_BUILD_DURING_DEPLOYMENT=false
SCM_ENABLE_DYNAMIC_INSTALL=false
SCM_POST_DEPLOYMENT_ACTIONS_PATH=PostDeploymentActions

In GitHub repo, added the following folder to the root: 'PostDeploymentActions'. Inside that folder, I added a start script 'start.cmd' with the following lines:

npm install
npm start
"

I'd reported this issue and similar issue was fixed for a few users by adding SCM_ENABLE_DYNAMIC_INSTALL=false application settings, kindly let me know if it works for you. Will follow-up with you further.
:0 1 Reputation point

2020-12-28T18:59:04.977+00:00

Hello, sorry I haven’t been able to respond, I ended up just using an Azure Virtual Machine instead to save the headache. However, I DO NOT recommend adding a PostDeploymentActions start script. This script will time out in the build actions, and the build status will fail. The script will also prevent any new updates from being deployed. You would also have to kill other node processes on the service, which could have unintended consequences.
ajkuma 28,036 Reputation points Microsoft Employee Moderator

2020-12-29T07:36:24.073+00:00

Thanks for the follow-up, 0-2838.

Apologies for any frustrating experiencing with this. I was hoping to connect with you to get to the root of the problem with your subscription details (privately). Kindly let me know if you need further assistance with this.
I worked on multiple similar issues and we were able to fix with just by adding this setting SCM_ENABLE_DYNAMIC_INSTALL=false.
I have shared this feedback with our product team. Once again sorry for any inconvenience!

Answer 1

meme 1

Just setting SCM_ENABLE_DYNAMIC_INSTALL=false works. It lets kudu fetch data from github to /tmp.

After that I was monitoring /home/site/deployment/.../log.log file
It looked like the deployment did run "react-scripts build" (from postinstall in package.json)
2020-12-26T20:12:59.8600243Z,> frontend@0.1.0 build /tmp/8d8a9d9e6dc5020/frontend,,0
2020-12-26T20:12:59.8805025Z,> react-scripts build,,0
2020-12-26T20:12:59.9019914Z,,,0
2020-12-26T20:13:15.2793888Z,Creating an optimized production build...,,0
Then about 10 minutes later it died with the following error:
2020-12-26T20:22:43.8661480Z,An unknown error has occurred. Check the diagnostic log for details.,cd82047b-aac7-4f6b-813a-fcb3fe60109e,2

Immediate after this, I checked /var/.../diagnosticLog, but there wasn't log file to look at...

N.B. my postinstall script
"postinstall": "cd frontend && npm install && npm run build",

ajkuma 28,036 Reputation points Microsoft Employee Moderator

2020-12-29T17:04:31.713+00:00

@meme , Thanks for the update. I'm not sure about the App Service Plan (ASP) you're leveraging, you may scale-up your ASP and then check to see if it works fine.
Just to confirm, how large is the deployment?
If the above doesn't help, I'll connect with you privately to fetch more information on your subscription, WebApp and log trace.

To keep you posted: In regards to this "error: cannot run ssh: No such file or directory\nfatal: unable to fork\n\n/usr/bin/git fetch origin --progress" during the deployment (~PHP 7.4/Node 14)- I have reported and relayed the feedback- our product team is working on a fix but no concrete ETA to share as of yet. At this time the workaround is to add 'SCM_ENABLE_DYNAMIC_INSTALL=false' app setting. As soon as I hear more information I'll post an update here. Thanks for your patience and collaboration on this.
meme 1 Reputation point

2020-12-29T17:51:07.7+00:00

The deployment size is as follows

du -hs src frontend/src
110K src
210K frontend/src

Files which "react-scripts build" was working are 210k.
thanks
ajkuma 28,036 Reputation points Microsoft Employee Moderator

2020-12-29T18:44:05.767+00:00

Thanks for the details, meme-8208. I have reached out you privately.
ajkuma 28,036 Reputation points Microsoft Employee Moderator

2021-01-02T06:00:43.093+00:00

Update: To benefit the community (Posting a public answer/with meme-8208 (thanks for your time and update).

Free Linux App Service tier was used (for demo). We observed high CPU usage during the build of React files as Post-deployment. Removed react-build script and deployed and copied the React files.

Share via

Cannot deploy NodeJS app from private GitHub repo

1 answer

Your answer