Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error deploying/starting business network on Composer Playground #119

Closed
odrodrig opened this issue Sep 28, 2018 · 1 comment
Closed

Error deploying/starting business network on Composer Playground #119

odrodrig opened this issue Sep 28, 2018 · 1 comment

Comments

@odrodrig
Copy link

odrodrig commented Sep 28, 2018

I followed this guide to deploy a HLFV1.1 network with composer on IBM Kubernetes Service but am getting the following error when trying to deploy a network:

Error trying to start business network. Error: No valid responses from any peers. Response from attempted peer comms was an error: Error: 2 UNKNOWN: error starting container: Failed to generate platform-specific docker build: Error returned from build: 1 "npm ERR! code ENOTFOUND npm ERR! errno ENOTFOUND npm ERR! network request to https://registry.npmjs.org/composer-common failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443 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! /root/.npm/_logs/2018-09-28T16_23_46_620Z-debug.log "

image

Steps to reproduce:

  1. Follow guide at https://ibm-blockchain.github.io/ for creating the network on a free cluster
  2. Go to your playground instance and try deploying a business network
@davidkel
Copy link

davidkel commented Oct 8, 2018

@odrodrig @timroster This is due to changes in the way IBM K8s handles creation of new containers now. Because of this change it no longer possible to run node.js chaincode in this environment.
As a result support for Composer has been removed and the scripts updated to reflect this.

@sstone1 sstone1 closed this as completed Oct 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants