Azure-docs: Follwoing guide fails deployment ENOENT: no such file or directory, open '/opt/nodejs/12.14.0/npm.txt'

Created on 27 Apr 2020 · 9Comments · Source: MicrosoftDocs/azure-docs

I've tried following this exact guide, using several Rails apps, several other guides on docs.microsoft.com, and several blog posts/medium articles on this topic, using both the CLI and the GUI, and they all result in the following deployment failure:

...
remote: Detecting node version spec...
remote: Using default version: 12.14.0
remote: Node.js versions available on the platform are: 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.16.3, 10.18.0, 12.9.1, 12.14.0.
remote: Resolved to version 12.14.0
remote: ENOENT: no such file or directory, open '/opt/nodejs/12.14.0/npm.txt'
remote: Detecting npm version spec...
remote: An error has occurred during web site deployment.
remote: select node version failed

I don't know enough about deploying apps to Azure to give much more information other than it appears that the first step in the build process seems to be failing to pick up Node. Nothing in any of these guides even mention node, even though it's required to correctly build a Rails app (assets processing).

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 7bb30245-963c-d1ec-76a9-66119c79fb1e
Version Independent ID: d3ee025c-ad6d-d8bd-84a2-9409f1a682f7
Content: Tutorial: Linux Ruby app with Postgres - Azure App Service
Content Source: articles/app-service/containers/tutorial-ruby-postgres-app.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

Pri2 app-servicsvc cxp escalated-product-team product-bug product-issue triaged

Source

ttilberg

👍1

Most helpful comment

Ugh I am getting "ENOENT: no such file or directory, open '/opt/nodejs/12.16.3/npm.txt'". Terrible. -_-

kevinclarkadstech on 27 Jul 2020

👍2 😕1

All 9 comments

@ttilberg
Thanks for the feedback! We are currently investigating and will get back on this.

VikasPullagura-MSFT on 28 Apr 2020

The product team is aware of the issue @ttilberg. I'm awaiting a response of when a fix will be deployed. I'll update you once I find out.

RyanHill-MSFT on 29 Apr 2020

Referencing a dupe issue: https://github.com/MicrosoftDocs/azure-docs/issues/53360

They discuss using Docker as a workaround, and also link to the Ruby app service container: https://github.com/Azure-App-Service/ruby

ttilberg on 6 May 2020

👍1

@ttilberg, the team is aware of the issue but no ETA on when a fix will be rolled out. If you can containerize your app as a workaround, I would advise going down that route.

RyanHill-MSFT on 7 May 2020

👎1

Product team is aware of this issues. we have a tracking issue in our backlog and are investigating options.

btardif on 12 May 2020

I ran into the same issue. Any updates?

cindywu on 23 Jun 2020

We have a fix for this that will be rolling out with the next app service deployment. ETA for this to rollout to prod is Sept

btardif on 7 Jul 2020

Ugh I am getting "ENOENT: no such file or directory, open '/opt/nodejs/12.16.3/npm.txt'". Terrible. -_-

kevinclarkadstech on 27 Jul 2020

👍2 😕1

Hi, If people are still facing this issue I would recommend trying to add the below app setting until a fix has been made.
WEBSITE_NPM_DEFAULT_VERSION=6.14.4