on 2021 Dec 16 11:28 AM
Hi,
I'm following the learning plan here: https://learning.sap.com/learning-journey/developing-with-sap-extension-suite/deploy-manually and I am facing issues.
When running cf push to push the app to my trial account. I'm getting the following errors.
npm ERR! code ENOTFOUND
npm ERR! syscall getaddrinfo
npm ERR! errno ENOTFOUND
npm ERR! network request to http://nginx-redirector.repo-cache.svc.cluster.local/repository/appstudio-npm-group/yallist/-/yallis... failed, reason: getaddrinfo ENOTFOUND nginx-redirector.repo-cache.svc.cluster.local
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! A complete log of this run can be found in:
npm ERR! /tmp/cache/final/.npm/_logs/2021-12-16T10_59_15_309Z-debug.log
**ERROR** Unable to build dependencies: exit status 1
Failed to compile droplet: Failed to run all supply scripts: exit status 14
Exit status 223
Cell cfeb172d-f2c7-42d1-a157-58148983025c stopping instance 6a8d2f73-d181-4569-b51b-03b4c12a79b6
Cell cfeb172d-f2c7-42d1-a157-58148983025c destroying container for instance 6a8d2f73-d181-4569-b51b-03b4c12a79b6
BuildpackCompileFailed - App staging failed in the buildpack compile phase
FAILED
I am sure that I have no network issues as the errors suggests. Can anyone shed some light on this?
Richie
Request clarification before answering.
Hi,
I think you are using SAP Business Application Studio and not SAP Web IDE, right?
The problem you are probably running into is, BAS creates a package-lock.json with URLs for the NPM repository, which cannot be resolved outside BAS. For example in the Cloud Foundry environment, when you deploy your app.
To avoid this problem, follow the steps in the accepted answer of How to avoid changes in package-lock.json when using local and BAS development in parallel?
In short: add a file named .npmrc to your project directory with the content
registry=https://registry.npmjs.com/
then run npm install again and you should notice in your package-lock.json that the repository URLs have changed from http://nginx-redirector.repo-cache.svc.cluster.local/repository/. to https://registry.npmjs.com/.
Kind regards,
Sebastian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
52 | |
8 | |
5 | |
5 | |
5 | |
5 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.