Closed ashishchandr70 closed 5 years ago
Hi @ashishchandr70, have you tried asking this question on the Hyperledger Rocket Chat https://chat.hyperledger.org? This is more of a Hyperledger Fabric question than a extension question.
Hi Caroline - yeah I asked this yesterday evening before I posted it here.
If you don't want to use a custom docker image then the only thing i can suggest is to use Go rather then Node
Hi Caroline - thanks for your suggestion. My colleague came up with a simpler fix - move the pem file to the source code folder where .npmrc lives and change the /path/to/pem to simply pem. That got me past the PEM file error. Thanks again @cazfletch
Disclaimer: This is a question - nothing is wrong with IBP extension.
Description
In our environment, we have restricted access to the internet from our Linux VMs. We use a local artifactory based repository which serves as our npm registry as well as our docker registry.
The access to this repo is via a certificate file, whose path is specified in the .npmrc.
I am using the bond sample contract, which I am able to install to local_fabric runtime. However, when it comes to instantiation, I get an error, which is expected as the ccenv (as far as I know) container knows nothing about our local filesystem and the files stored there.
I also don't want to create custom container images (if I can help it), so was wondering if you all have any suggestions.
Expected Behavior
I expect to get an error on the pem file as it is a local file and the container knows nothing about it.
Actual Behavior
Instantiation fails.
Possible Fix
Steps to Reproduce
Start VS Code
Start Local Fabric runtime.
Create a sample contract and install it on local_fabric
Instantiate the contract
Existing issues
983
978
962
Log File
Your Environment
IBM Blockchain Platform Extension Version: 1.0.5
Visual Studio Code version: 1.36.1
Environment name and version : Nodejs v8.16.0, npm v6.4.1
Operating System and version: RHEL v7.6 (Maipo)