WebPSA error when deploying linux-dev - (Failed to start 'npm')
See original GitHub issueHi,
I’ve an issue when using WebSPA and deploying the linux-dev image. WebSPA container starts but is unable to process requests since npm seems to not beeing installed on the container:
AggregateException: One or more errors occurred. (Failed to start 'npm'. To resolve this:.
[1] Ensure that 'npm' is installed and can be found in one of the PATH directories.
Current PATH enviroment variable is: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
Make sure the executable is in one of those directories, or update your PATH.
Regarding the Dokerfile code, it seems to be normal because the image uses aspnet:6.0 which does not contain nodejs or npm.
Issue Analytics
- State:
- Created a year ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Failed to start 'npm': Ensure that 'npm' is installed and can ...
In Visual Studio 2019 v16.4.1 when attempting to run a ASP.NET Core Web Application with React installed I get an error in the...
Read more >Web pack Error while running a npm start && npm run build ...
Bug report I am using MacOs 11.2.1 and I have tried to install / run and deploy react-storefront using several methods. All have...
Read more >Deploy Node web app Error
Hello I am new to Render and have encountered an issue while trying to deploy my repository to Render. I'm not quite sure...
Read more >Common errors
Possible temporary npm registry glitch, or corrupted local server cache. Run npm cache clean and/or try again later. This can be caused by...
Read more >Error while deploying Node.js app - Questions / Help
I tried to deploy it using the command fly deploy --local-only using Docker locally and I got this error: => ERROR [build 3/5]...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes, it works when specifying to production. That was the reason I created the PR #1984
This issue just happened to me, changing the value in the helm chart fixed it. But I didnt see any references to documentation here https://github.com/dotnet-architecture/eShopOnContainers/wiki/Deploy-to-Azure-Kubernetes-Service-(AKS). Do you still plan to update the docs or would it be better to update the helm chart itself?