2016-05-13 72 views
1

我的演示项目已经运行好了,但它只是网络中的一个对等设备。我想在网络中添加更多的对等点。 我遵循本指南==>https://github.com/hyperledger-archives/fabric/blob/540c4db5f64dba4bd1b18e896c96a8d17d7ec552/docs/dev-setup/devnet-setup.md在Hyperledger Fabric中设置网络开发v0.5-preview

请亲切帮助检查下面的日志, 该目录是错误的?或者什么是正确的方式来运行这个同行的启动?

[email protected]:v-:/opt/gopath/src/github.com/hyperledger/fabric$ docker run --rm -it -e CORE_VM_ENDPOINT=http://172.17.0.1:2375 -e CORE_PEER_ID=vp0 -e CORE_PEER_ADDRESSAUTODETECT=true hyperledger-peer peer node start 
Unable to find image 'hyperledger-peer:latest' locally 
Pulling repository docker.io/library/hyperledger-peer 
docker: Error: image library/hyperledger-peer not found. 
See 'docker run --help'. 
+0

可以添加你,当你运行'泊坞窗images'你会得到什么? –

回答

1

是否有可能网络中的第一个节点在Docker容器中启动? (例如,它可以作为使用peer node start的过程开始)

我们可以验证哪些泊坞窗图像在流浪机中可用。只要运行docker images命令:

[email protected]:v0.0.9-b4acc4b:$ docker images 
REPOSITORY      TAG     IMAGE ID   CREATED    SIZE 
hyperledger/fabric-baseimage latest    c1d6f4800a55  27 hours ago  1.297 GB 
hyperledger/fabric-baseimage x86_64-0.0.9  70328eed56aa  2 weeks ago   990.1 MB 
busybox      latest    47bcc53f74dc  9 weeks ago   1.113 MB 

有了这样的配置,当“hyperledger等”形象是不可用,验证同伴不会因为“无法找到像”错误开始:

[email protected]:v0.0.9-b4acc4b:/opt/gopath/src/github.com/hyperledger/fabric/peer$ docker run --rm -it -e CORE_VM_ENDPOINT=http://172.17.0.1:2375 -e CORE_PEER_ID=vp0 -e CORE_PEER_ADDRESSAUTODETECT=true hyperledger-peer peer node start 
Unable to find image 'hyperledger-peer:latest' locally 
Pulling repository docker.io/library/hyperledger-peer 
docker: Error: image library/hyperledger-peer not found. 

“hyperledger等:最新的”:

cd $GOPATH/src/github.com/hyperledger/fabric/core/container 
go test -run BuildImage_Peer 

现在docker images应该表现出一个更可用的图像:图像可以通过创建

REPOSITORY      TAG     IMAGE ID   CREATED    SIZE 
hyperledger-peer    latest    438b65f18f21  8 seconds ago  1.418 GB 

在这一点上验证同行应该成功启动:

[email protected]:v0.0.9-b4acc4b:~$ docker run —rm -it -e CORE_VM_ENDPOINT=http://172.17.0.1:2375 -e CORE_PEER_ID=vp0 -e CORE_PEER_ADDRESSAUTODETECT=true hyperledger-peer peer node start 
21:55:51.969 [crypto] main -> INFO 001 Log level recognized 'info', set to INFO 
21:55:51.970 [peer] func1 -> INFO 002 Auto detected peer address: 172.17.0.2:30303 
21:55:51.971 [peer] func1 -> INFO 003 Auto detected peer address: 172.17.0.2:30303 
21:55:51.972 [peer] func1 -> INFO 004 Auto detected peer address: 172.17.0.2:30303 
21:55:51.974 [main] serve -> INFO 005 Security enabled status: false 
21:55:51.974 [main] serve -> INFO 006 Privacy enabled status: false 
… 
相关问题