Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure App Service Node.js Deployment Reports node_modules not found #386

Closed
capraynor opened this issue Oct 12, 2019 · 5 comments
Closed

Comments

@capraynor
Copy link

capraynor commented Oct 12, 2019

Bug Report

  • At what date and time did you most recently experience the problem?

11:00 Oct. 12, 2019 GMT +8

  • Where did you experience the problem? E.g. Azure Web Apps, Azure Functions, Azure Container Registry, or offline use.

Azure App Service

I think that this is caused by making symbolic link to /node_modules that I suggested in another issue.

  • What did you expect or want to happen?

The deployment should be correctly executed.

  • How can we reproduce it?

Well I think that you can hack into my app service.

  • Do you have log output? Please include between the backticks:
[Step 1/1] remote: Deploy Async        
[05:35:07]	[Step 1/1] remote: Updating branch 'master'.        
[05:35:08]	[Step 1/1] remote: Updating submodules.        
[05:35:08]	[Step 1/1] remote: Preparing deployment for commit id '10b08ded5c'.        
[05:35:09]	[Step 1/1] remote: Oryx-Build: Running kudu sync...        
[05:35:10]	[Step 1/1] remote: Kudu sync from: '/home/site/repository' to: '/home/site/wwwroot'        
[05:35:10]	[Step 1/1] remote: Error: ENOENT: no such file or directory, stat '/home/site/wwwroot/node_modules'        
[05:35:11]	[Step 1/1] remote: App container will begin restart within 10 seconds.        
[05:35:11]	[Step 1/1] remote: Deployment Logs : 'https://forguncy-api-test.scm.azurewebsites.net/newui/jsonviewer?view_url=/api/deployments/10b08ded5c85ff67658365b853072b461f5b7b28/log'        
[05:35:11]	[Step 1/1] To https://forguncy-api-test.scm.azurewebsites.net:443/forguncy-api-test.git
[05:35:11]	[Step 1/1]  + eff6468...10b08de master -> master (forced update)
@rich521
Copy link

rich521 commented Oct 13, 2019

Same issue as well:
Command: kudusync -v 50 -f /home/site/repository -t /home/site/wwwroot -n /home/site/deployments/6b56eaa9c155c21279fd47b3ef4dd597997345ee/manifest -p /opt/Kudu/Scripts/firstDeploymentManifest -i ".git;.hg;.deployment;.deploy.sh" Kudu sync from: '/home/site/repository' to: '/home/site/wwwroot' Error: ENOENT: no such file or directory, stat '/home/site/wwwroot/node_modules' \n/opt/Kudu/Scripts/starter.sh kudusync -v 50 -f /home/site/repository -t /home/site/wwwroot -n /home/site/deployments/6b56eaa9c155c21279fd47b3ef4dd597997345ee/manifest -p /opt/Kudu/Scripts/firstDeploymentManifest -i ".git;.hg;.deployment;.deploy.sh"

@beb3704
Copy link

beb3704 commented Oct 14, 2019

I'm having the same issue. Any fix for this? I can't update any of my sites.

@capraynor
Copy link
Author

capraynor commented Oct 15, 2019

Please read official response in here:
projectkudu/kudu#2946 (comment)

@sanchitmehta
Copy link
Member

This has been fixed and Kudu has been patched for all affected customers.

@capraynor
Copy link
Author

Yes thanks for solving this issue, I'll close this bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants