Error: pathspecs with curl -sSL [shortened-url-here] | bash -s 1.1.0 - hyperledger-fabric

According to hyperledger-composer tutorial, to deploy network with multi-organization I need to clean previous installation of composer:
cd ~/fabric-dev-servers
./stopFabric.sh
./teardownFabric.sh
After that, I cloned hyperledger/fabric-sample branch
git clone -b issue-6978 https://github.com/sstone1/fabric-samples.git
Then, navigate to fabric-sample and download specific binaries from the repository with shortened link
curl -sSL [shortened-url-here] | bash -s 1.1.0
Right after that, one error thrown
===> Checking out v1.1.0 branch of hyperledger/fabric-samples
error: pathspec 'v1.1.0' did not match any file(s) known to git.
Plus, there some more relating to several images
Error response from daemon: manifest for hyperledger/fabric-ca:x86_64-1.2.0-rc1 not found
Error response from daemon: No such image: hyperledger/fabric-ca:x86_64-1.2.0-rc1
===> Pulling thirdparty docker images
==> THIRDPARTY DOCKER IMAGE: couchdb
Error response from daemon: manifest for hyperledger/fabric-couchdb:x86_64-0.4.8 not found
Error response from daemon: No such image: hyperledger/fabric-couchdb:x86_64-0.4.8
==> THIRDPARTY DOCKER IMAGE: kafka
Error response from daemon: manifest for hyperledger/fabric-kafka:x86_64-0.4.8 not found
Error response from daemon: No such image: hyperledger/fabric-kafka:x86_64-0.4.8
==> THIRDPARTY DOCKER IMAGE: zookeeper
Error response from daemon: manifest for hyperledger/fabric-zookeeper:x86_64-0.4.8 not found
Error response from daemon: No such image: hyperledger/fabric-zookeeper:x86_64-0.4.8
I also attach with the full result of above errors
bp1#bp1-VirtualBox:~/fabric-dev-servers/fabric-samples$ curl -sSL [shortened-url here] | bash -s 1.1.0
Installing hyperledger/fabric-samples repo
===> Checking out v1.1.0 branch of hyperledger/fabric-samples
error: pathspec 'v1.1.0' did not match any file(s) known to git.
Installing Hyperledger Fabric binaries
===> Downloading version x86_64-1.1.0 platform specific fabric binaries
===> Downloading: https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/hyperledger-fabric/linux-amd64-1.1.0/hyperledger-fabric-linux-amd64-1.1.0.tar.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 35.4M 100 35.4M 0 0 145k 0 0:04:09 0:04:09 --:--:-- 135k
==> Done.
===> Downloading version x86_64-1.2.0-rc1 platform specific fabric-ca-client binary
===> Downloading: https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric-ca/hyperledger-fabric-ca/linux-amd64-1.2.0-rc1/hyperledger-fabric-ca-linux-amd64-1.2.0-rc1.tar.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 4939k 100 4939k 0 0 153k 0 0:00:32 0:00:32 --:--:-- 205k
==> Done.
Installing Hyperledger Fabric docker images
===> Pulling fabric Images
==> FABRIC IMAGE: peer
x86_64-1.1.0: Pulling from hyperledger/fabric-peer
Digest: sha256:57417699ddf50c5ebd47a9a2cc74c0324fbba0281eb1104b9ddd05a67776b01f
Status: Image is up to date for hyperledger/fabric-peer:x86_64-1.1.0
==> FABRIC IMAGE: orderer
x86_64-1.1.0: Pulling from hyperledger/fabric-orderer
Digest: sha256:0c3a3b5ecfd24b513da22bbb77da7b3f5bca9c121cc0ac5c46ba04c97c163654
Status: Image is up to date for hyperledger/fabric-orderer:x86_64-1.1.0
==> FABRIC IMAGE: ccenv
x86_64-1.1.0: Pulling from hyperledger/fabric-ccenv
Digest: sha256:07818367dc6d4264472d24b21819f9dc4e16e890d81ddfacee0341a22d72050b
Status: Image is up to date for hyperledger/fabric-ccenv:x86_64-1.1.0
==> FABRIC IMAGE: tools
x86_64-1.1.0: Pulling from hyperledger/fabric-tools
1be7f2b886e8: Already exists
6fbc4a21b806: Already exists
c71a6f8e1378: Already exists
4be3072e5a37: Already exists
06c6d2f59700: Already exists
4d536120d8a5: Already exists
0baaf9ec263e: Already exists
3ea9b6cc6f21: Already exists
6173b9a5fe5e: Already exists
e73719e0bcbe: Already exists
b55408c6ced5: Already exists
1a8bca84adfa: Pull complete
b54c1992cc9c: Pull complete
68093aff3e84: Pull complete
3827dc0ff46d: Pull complete
1e22360bf4e7: Pull complete
Digest: sha256:36d7fa8e8ddcc19fed8e1c3c06bc6ae1dac18c35e8a884188d2c08df3e5a4472
Status: Downloaded newer image for hyperledger/fabric-tools:x86_64-1.1.0
===> Pulling fabric ca Image
==> FABRIC CA IMAGE
Error response from daemon: manifest for hyperledger/fabric-ca:x86_64-1.2.0-rc1 not found
Error response from daemon: No such image: hyperledger/fabric-ca:x86_64-1.2.0-rc1
===> Pulling thirdparty docker images
==> THIRDPARTY DOCKER IMAGE: couchdb
Error response from daemon: manifest for hyperledger/fabric-couchdb:x86_64-0.4.8 not found
Error response from daemon: No such image: hyperledger/fabric-couchdb:x86_64-0.4.8
==> THIRDPARTY DOCKER IMAGE: kafka
Error response from daemon: manifest for hyperledger/fabric-kafka:x86_64-0.4.8 not found
Error response from daemon: No such image: hyperledger/fabric-kafka:x86_64-0.4.8
==> THIRDPARTY DOCKER IMAGE: zookeeper
Error response from daemon: manifest for hyperledger/fabric-zookeeper:x86_64-0.4.8 not found
Error response from daemon: No such image: hyperledger/fabric-zookeeper:x86_64-0.4.8
===> List out hyperledger docker images
hyperledger/fabric-ca x86_64-1.1.0 72617b4fa9b4 3 months ago 299MB
hyperledger/fabric-tools latest b7bfddf508bc 3 months ago 1.46GB
hyperledger/fabric-tools x86_64-1.1.0 b7bfddf508bc 3 months ago 1.46GB
hyperledger/fabric-orderer latest ce0c810df36a 3 months ago 180MB
hyperledger/fabric-orderer x86_64-1.1.0 ce0c810df36a 3 months ago 180MB
hyperledger/fabric-peer latest b023f9be0771 3 months ago 187MB
hyperledger/fabric-peer x86_64-1.1.0 b023f9be0771 3 months ago 187MB
hyperledger/fabric-ccenv latest c8b4909d8d46 3 months ago 1.39GB
hyperledger/fabric-ccenv x86_64-1.1.0 c8b4909d8d46 3 months ago 1.39GB
hyperledger/fabric-baseimage x86_64-0.4.6 dbe6787b5747 4 months ago 1.37GB
hyperledger/fabric-couchdb x86_64-0.4.6 7e73c828fc5b 4 months ago 1.56GB
Please kindly share some advice, thanks in advance.

Due to recent Fabric changes, there is a change in behaviour that we should capture in the tutorial..
Please try curl -sSL [shortened-url-here] | bash -s 1.1.0 1.1.0 0.4.6 - ie 3 parameters, separated by spaces, to the bash -s command above and specifically those versions.
You can ignore the error: pathspec 'v1.1.0' message for now, as we're using a custom repo for the tutorial.

You can manually pull all those images. (Errors because of wrong version no in the script)
docker pull hyperledger/fabric-couchdb:x86_64-1.0.0
docker pull hyperledger/fabric-ca:x86_64-1.1.0

Related

ERROR: manifest for hyperledger/fabric-peer:latest not found: manifest unknown: manifest unknown

ERROR: manifest for hyperledger/fabric-peer:latest not found: manifest unknown: manifest unknown
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
fac6da40e9dc hello-world "/hello" 2 hours ago Exited (0) 2 hours ago nervous_merkle
04dc148ec933 9d418bac6a03 "/bin/sh -c 'apt-get…" 3 days ago Exited (100) 3 days ago wonderful_dewdney
ad04a161f30d gliderlabs/logspout "/bin/logspout" 4 weeks ago
Change the tag from latest to x86_64-1.0.2 in the compose file. There is no latest tag for this image. You can get all available tags on below link
https://hub.docker.com/r/hyperledger/fabric-peer/tags/
first Execute this command
docker pull hyperledger/fabric-peer:2.4
Next Execute this command
docker tag hyperledger/fabric-peer:2.4 hyperledger/fabric-peer:latest

composer network install command gives error as Error: 14 UNAVAILABLE: EOF

I am using Hyperledger Composer version v0.19.9 and Hyperledger Fabric version v1.1.
I have setup my blockchain network using Fabric and made all docker containers up and running. Following docker containers are running:
1. cli
2. orderer.sterlite.com
3. peer0.orga.sterlite.com
4. ca.orga.sterlite.com
5. peer0.orgb.sterlite.com
I have created a Peer Admin card using Composer CLI named PeerAdminOrgA#sterlite.
Now, when I try to install a business network using below command, I am getting an error:
composer network install -c PeerAdminOrgA#sterlite -a com-fab-bn.bna
Following is the error:
safvan#safvan-VirtualBox:~/blockchain/fabric-sdk/fabric-sdk-go/src/github.com/sterliteChain/config$ composer network install -c PeerAdminOrgA#sterlite -a com-fab-bn.bna
Installing business network. This may take a minute...
Error: Error trying install business network. Error: No valid responses from any peers.
Response from attempted peer comms was an error: Error: 14 UNAVAILABLE: EOF
Command failed
Following is the outcome of docker ps command:
safvan#safvan-VirtualBox:~/blockchain/fabric-sdk/fabric-sdk-go/src/github.com/sterliteChain/config$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
3645759c804d hyperledger/fabric-tools:latest "/bin/bash" About a minute ago Up About a minute cli
7f72016afeef hyperledger/fabric-orderer:latest "orderer" 19 hours ago Up About a minute 0.0.0.0:7050->7050/tcp orderer.sterlite.com
74f6a3c3f493 hyperledger/fabric-peer:latest "peer node start" 19 hours ago Up About a minute 0.0.0.0:7051->7051/tcp, 0.0.0.0:7053->7053/tcp peer0.orga.sterlite.com
6c3ab687ec95 hyperledger/fabric-ca:latest "sh -c 'fabric-ca-seâ¦" 19 hours ago Up About a minute 0.0.0.0:7054->7054/tcp ca.orga.sterlite.com
c6187a82e300 hyperledger/fabric-peer:latest "peer node start" 19 hours ago Up About a minute 0.0.0.0:9051->7051/tcp, 0.0.0.0:9053->7053/tcp peer0.orgb.sterlite.com
Kindly help me fix this issue.

Running composer network install in Hyperledger throws out an error

I am trying to deploy BNA to Fabric but getting this error
$ composer network install -c PeerAdmin#hlfv1 -a ~/Downloads/comment-network.bna
✖ Installing business network. This may take a minute...
Error: Error trying install business network. Error: No valid responses from any peers.
Response from attempted peer comms was an error: Error: 14 UNAVAILABLE: Connect Failed
Command failed
Already got docker running.
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
4a1452a6773a hyperledger/fabric-peer:x86_64-1.1.0 "peer node start" 14 minutes ago Up 14 minutes 0.0.0.0:7051->7051/tcp, 0.0.0.0:7053->7053/tcp peer0.org1.example.com
59221c711615 hyperledger/fabric-ca:x86_64-1.1.0 "sh -c 'fabric-ca-se…" 14 minutes ago Up 14 minutes 0.0.0.0:7054->7054/tcp ca.org1.example.com
eec390a547e5 hyperledger/fabric-couchdb:x86_64-0.4.6 "tini -- /docker-ent…" 14 minutes ago Up 14 minutes 4369/tcp, 9100/tcp, 0.0.0.0:5984->5984/tcp couchdb
c7d462facea6 hyperledger/fabric-orderer:x86_64-1.1.0 "orderer" 14 minutes ago Up 14 minutes 0.0.0.0:7050->7050/tcp orderer.example.com
I installed Fabric using step 4 of this guide then ran
./startFabric.sh
./createPeerAdminCard.sh
prior to deploying BNA.
EDIT:
$ docker -v
Docker version 18.02.0-ce, build fc4de44
$ system_profiler SPSoftwareDataType
Software:
System Software Overview:
System Version: macOS 10.13.2 (17C88)
Kernel Version: Darwin 17.3.0
Boot Volume: Macintosh HD
Boot Mode: Normal
Computer Name: COMPUTER NAME
User Name: USERNAME
Secure Virtual Memory: Enabled
System Integrity Protection: Enabled
Time since boot: 13 days 18:28
I concluded that my issue was because of me using docker-machine to run Docker instead of running Docker via daemon.
I solved it by adding the ports used to VirtualBox.

No valid responses from any peers while deploying the BNA file with "composer network start"

I am following the link: https://hyperledger.github.io/composer/tutorials/deploy-to-fabric-multi-org to deploy bna file in 2 different peers.
Up to step-16 everything is working fine, but when I am trying to deploy the .bna file getting following error.
After importing the identity cards to composer when I have run "install runtime" command for Org1, it is successfully processed but when I am running for Org2 it is showing "No valid responses from any peers" error.
Following are the output.
amandai#ubuntultop:~/block chain/fabric-samples V1/ess-multipeer-sample/network$ composer network start -c PeerAdmin#amsnetwork-essbbsr -a amsnetwork.bna -o endorsementPolicyFile=endorsement-policy.json -A chinmayak -C chinmayak/admin-pub.pem -A kkumarbabu -C kkumarbabu/admin-pub.pem
Starting business network from archive: amsnetwork.bna
Business network definition:
Identifier: amsnetwork#0.2.0-20180102082548
Description: The Hello World of Hyperledger Composer samples
Processing these Network Admins:
userName: chinmayak
userName: kkumarbabu
✖ Starting business network definition. This may take a minute...
Error: Error trying to instantiate composer runtime. Error: No valid responses from any peers.
Response from attempted peer comms was an error: Error: REQUEST_TIMEOUT
Response from attempted peer comms was an error: Error: REQUEST_TIMEOUT
Command failed
Even all the peers are up.
amandai#ubuntultop:~/block chain/fabric-samples V1/ess-multipeer-sample/network$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
c83e1a245386 hyperledger/fabric-tools "/bin/bash -c './s..." 6 minutes ago Up 6 minutes cli
46bf68ca719e hyperledger/fabric-peer "peer node start" 6 minutes ago Up 6 minutes 0.0.0.0:8051->7051/tcp, 0.0.0.0:8053->7053/tcp peer0.ezone.esspl.com
2e740ce743fe hyperledger/fabric-ca "sh -c 'fabric-ca-..." 6 minutes ago Up 6 minutes 0.0.0.0:7054->7054/tcp ca_peerEssbbsr
cc48b8ee44db hyperledger/fabric-orderer "orderer" 6 minutes ago Up 6 minutes 0.0.0.0:7050->7050/tcp orderer.esspl.com
46077fc3888a hyperledger/fabric-peer "peer node start" 6 minutes ago Up 6 minutes 0.0.0.0:7051->7051/tcp, 0.0.0.0:7053->7053/tcp peer0.essbbsr.esspl.com
3f65239e7315 hyperledger/fabric-ca "sh -c 'fabric-ca-..." 6 minutes ago Up 6 minutes 0.0.0.0:8054->7054/tcp ca_peerEzone
Please help how to resolve this. Thanks
I did the following modification in "peer-base.yaml" file and issue has been resolved.
- CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=${COMPOSE_PROJECT_NAME}_byfn
To
- CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=network_amsnetwork
Here "network_amsnetwork" is the network name. You can find your network name by using "docker network ls" command

Docker on RHEL 7 in AWS can’t pull images

We're looking to incorporate docker on our project and I'm having some difficulty.
I installed Docker via the instructions here: https://docs.docker.com/engine/installation/linux/rhel/ and had no problems. However, when I try to pull any images from docker hub, it just hangs and nothing ever happens:
┌─[user#hostname]─(~)
└─[11:53]$ docker pull alpine:latest
Here's my docker version info:
┌─[user#hostname]─(~)
└─[11:53]$ docker version
Client:
Version: 1.11.2
API version: 1.23
Go version: go1.5.4
Git commit: b9f10c9
Built: Wed Jun 1 21:23:11 2016
OS/Arch: linux/amd64
Server:
Version: 1.11.2
API version: 1.23
Go version: go1.5.4
Git commit: b9f10c9
Built: Wed Jun 1 21:23:11 2016
OS/Arch: linux/amd64
This is a redhat 7.2 instance in a VPC. I'm using another rhel 7.2 instance to handle NAT through iptables. This issue is the first connectivity problem I've had.
I read elsewhere that specifying an http proxy would solve the issue, so I set up a squid proxy on my nat server, but to no avail. I followed the instructions here to set the proxy for docker to use: https://docs.docker.com/engine/admin/systemd/#/http-proxy
The proxy is getting the requests, but docker still can't pull any images. Here's the out put of my squid logs:
1467475616.376 110 10.0.0.50 TCP_MISS/200 3250 CONNECT registry-1.docker.io:443 - HIER_DIRECT/52.71.80.248 -
1467475616.415 35 10.0.0.50 TCP_MISS/200 4444 CONNECT auth.docker.io:443 - HIER_DIRECT/52.204.167.32 -
I'm running out of things to try here. Any help would be greatly appreciated.
EDIT
Got a new error! After tweaking the squid proxy configuration, I now get this error when attempting to pull an image:
┌─[user#hostname]─(~)
└─[15:15]$ sudo docker pull alpine
Using default tag: latest
Pulling repository docker.io/library/alpine
Error while pulling image: Get https://index.docker.io/v1/repositories/library/alpine/images: Service Unavailable
Here's the output of ping:
┌─[user#hostname]─(~)
└─[15:15]$ ping index.docker.io
PING us-east-1-elbio-rm5bon1qaeo4-623296237.us-east-1.elb.amazonaws.com (54.173.200.203) 56(84) bytes of data.
^C
--- us-east-1-elbio-rm5bon1qaeo4-623296237.us-east-1.elb.amazonaws.com ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 1999ms
And wget can download a json file from the url in the docker error message:
┌─[user#hostname]─(~)
└─[15:17]$ wget https://index.docker.io/v1/repositories/library/alpine/images
--2016-07-02 15:17:20-- https://index.docker.io/v1/repositories/library/alpine/images
Resolving index.docker.io (index.docker.io)... 54.173.200.203, 52.22.190.106, 52.203.138.237
Connecting to index.docker.io (index.docker.io)|54.173.200.203|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/json]
Saving to: ‘images’
[ <=> ] 6,900 --.-K/s in 0s
2016-07-02 15:17:20 (185 MB/s) - ‘images’ saved [6900]

Resources