How to fix version mismatch between runtime node version and actual node version

Question

How to fix version mismatch between runtime node version and actual node version

Mohamed Elsagh 0

These are the settings on my web app User's image

However my deployments were never successful. Then I find this on the websites' bash:
User's image

How is that the case? And how do I fix this? I never specified v18 in any of my work on this webapp, not once.

Mohamed Elsagh 0 Reputation points

2023-12-03T23:31:41.4366667+00:00

clarification: deployments were successful, I just could not see the web app live

1 answer

Your answer

Mohamed Elsagh 0 Reputation points

2023-12-03T23:31:41.4366667+00:00

clarification: deployments were successful, I just could not see the web app live

Answer 1

Ryan Hill 30,281 Microsoft Employee Moderator

@Mohamed Elsagh

Check your package.json or local node version. It may be referring to an older version of node. You'll notice I created a web app using Node 20 but was changed to match the runtime version on my local machine. To fix, make sure your local environment and package.json is using Node 20.

appsvclinux ssh host

vscode terminal

--

EDIT 2023 Dec 6 Based off your I'm updating my answer. I have verified the following steps do indeed work.

Set the runtime in either the portal or run az webapp config set --name <app name> --resource-group <resource group> --linux-fx-version "NODE|20-lts". If using PowerShell, use --% to escape the | in --linux-fx-version argument.
Restart the app service either via portal or az webapp restart --name <app name> --resource-group <resource group>

When you start a new SSH session, you should see the NodeJS version updated upon the start of the session.

Mohamed Elsagh 0 Reputation points

2023-12-06T04:53:16.32+00:00

My local node is 20.9.0,
the web app was created using that version. In the package.json nothing specified the use of node 20+ so I added the following:

Still the same issue, here is a log snapshot:

From the get go the Azure web app is using node 18, there is no "updating runtime version" message.
Its important to re-iterate here that my node stack is set to 20 on the Azure webapp.
Ryan Hill 30,281 Reputation points Microsoft Employee Moderator

2023-12-06T17:28:28.3466667+00:00

@Mohamed Elsagh , I've updated my answer above. Since the portal already shows Node 20-lts, restart the web app and recheck. If that doesn't work, toggle the node version and then restart.
Ryan Hill 30,281 Reputation points Microsoft Employee Moderator

2023-12-06T20:23:24.4366667+00:00

@Mohamed Elsagh check my updated response above.
Mohamed Elsagh 0 Reputation points

2023-12-08T05:08:58.1966667+00:00

Hello, I tried both approaches and none worked. the node -v command is always giving 18.17.1
This was the powershell's commands output and I restated the webapp as you said afterwards

Ryan Hill 30,281 Microsoft Employee Moderator

I wasn't able to replicate your issue. Check the docker logs of your app service. After changing the runtime and restarting the app service, you should see output similar to this:

2023-12-08T19:45:58.136Z INFO  - 18-lts_20230908.2.tuxprod Pulling from appsvc/node
2023-12-08T19:45:58.173Z INFO  - 6a70103cc499 Pulling fs layer
2023-12-08T19:45:58.174Z INFO  - ccb4221e2c63 Pulling fs layer
...
2023-12-08T19:51:15.290Z INFO  - Recycling container because of AppFrameworkVersionChange and appFrameworkVersion = 20-lts
2023-12-08T19:51:19.105Z INFO  - 20-lts_20231109.3.tuxprod Pulling from appsvc/node
2023-12-08T19:51:19.121Z INFO  - 0a9573503463 Pulling fs layer
2023-12-08T19:51:19.131Z INFO  - 1ccc26d841b4 Pulling fs layer

If you don't see anything like that, try creating a separate app service, but don't delete this one. We'll need to work more closely with you to determine why the image isn't being pulled as expected.

Mohamed Elsagh 0 Reputation points

2023-12-09T02:12:03.75+00:00

could not find that log for that app service. I did create a new one and I noticed that the KudoLite Bash tool gave v18 and the ssh tool gave v20, not sure why that is, I had them open concurrently
Mohamed Elsagh 0 Reputation points

2023-12-09T02:14:46.94+00:00

I added a new comment in the answers section
Ryan Hill 30,281 Reputation points Microsoft Employee Moderator

2023-12-10T22:42:06.8166667+00:00

@Mohamed Elsagh the docker logs are located under https://<app-name>.scm.azurewebsites.net/api/logs/docker. As far as KuduLite, that wouldn't be the container app that you're running...but the host that's running on top, which is responsible for your kudu builds and what not, i.e., different shell.

Share via

How to fix version mismatch between runtime node version and actual node version

1 answer

Your answer