peer deployCC of asset-transfer-basic has a parsing error while building docker image for javascript

[ss4adam]

Hyperledger fabric version 2 (tried this on 2.2 and 2.3) "writing your first application" seems to have a parsing error when pulling down docker image definition for the javascript image. The step fails when trying to build the image. This does not happen for golang.

running the following :
./network.sh deployCC -ccn basic -ccp ../asset-transfer-basic/chaincode-javascript/ -ccl javascript

results in:

Chaincode is packaged
Installing chaincode on peer0.org1...
Using organization 1
+ peer lifecycle chaincode install basic.tar.gz
+ res=1
Error: chaincode install failed with status: 500 - failed to invoke backing implementation of 'InstallChaincode': could not build chaincode: docker build failed: docker image build failed: docker build failed: Error returned from build: 1 "+ INPUT_DIR=/chaincode/input
+ OUTPUT_DIR=/chaincode/output
+ cp -R /chaincode/input/src/. /chaincode/output
+ cd /chaincode/output
+ '[' -f package-lock.json -o -f npm-shrinkwrap.json ]
+ npm install --production
npm ERR! code EAI_AGAIN
npm ERR! errno EAI_AGAIN
npm ERR! request to https://registry.npmjs.org/fabric-contract-api failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2021-02-25T16_45_02_077Z-debug.log
"
Chaincode installation on peer0.org1 has failed
Deploying chaincode failed

The more interesting contents are shown after opening /root/.npm/_logs/2021-02-25T16_45_02_077Z-debug.log

 0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/root/.nvm/versions/node/v12.16.1/bin/node',
1 verbose cli   '/root/.nvm/versions/node/v12.16.1/bin/npm',
1 verbose cli   'install',
1 verbose cli   'fabric-contract-api'
1 verbose cli ]
2 info using npm@6.13.4
3 info using node@v12.16.1
4 verbose npm-session 631c0be477b9cf75
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 timing stage:rollbackFailedOptional Completed in 4ms
8 timing stage:runTopLevelLifecycles Completed in 16ms
9 verbose stack Error: Failed to parse json
9 verbose stack Unexpected end of JSON input while parsing near ''
9 verbose stack     at parseError (/root/.nvm/versions/node/v12.16.1/lib/node_modules/npm/node_modules/read-package-json/read-json.js:470:11)
9 verbose stack     at parseJson (/root/.nvm/versions/node/v12.16.1/lib/node_modules/npm/node_modules/read-package-json/read-json.js:105:26)
9 verbose stack     at /root/.nvm/versions/node/v12.16.1/lib/node_modules/npm/node_modules/read-package-json/read-json.js:52:5
9 verbose stack     at /root/.nvm/versions/node/v12.16.1/lib/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:115:16
9 verbose stack     at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
10 verbose cwd /usr/local/bin
11 verbose Linux 3.10.0-1160.11.1.el7.x86_64
12 verbose argv "/root/.nvm/versions/node/v12.16.1/bin/node" "/root/.nvm/versions/node/v12.16.1/bin/npm" "install" "fabric-contract-api"
13 verbose node v12.16.1
14 verbose npm  v6.13.4
15 error code EJSONPARSE
16 error file /usr/local/bin/package.json
17 error JSON.parse Failed to parse json
17 error JSON.parse Unexpected end of JSON input while parsing near ''
18 error JSON.parse Failed to parse package.json data.
18 error JSON.parse package.json must be actual JSON, not just JavaScript.
19 verbose exit [ 1, true ]

Running CentOS7 and Docker Version: 20.10.2 API version: 1.41

[lindluni]

Hello @ss4adam

Discussions are a way to collaborate on the fabric codebase, bugs such as this one should be opened in Jira

Thank you!