未找到Hyperledger Docker端点 [英] Hyperledger Docker endpoint not found

查看:153
本文介绍了未找到Hyperledger Docker端点的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已经在Ubuntu 14.04上设置了一个使用Docker映像的2节点Hyperledger网络,方法是按照@ http://hyperledger-fabric.readthedocs.io/en/latest/Setup/Network-setup/#leveraging-published-docker-images



然后,我尝试部署链式代码,通过调用POST / chaincode API来编译链接代码,并获得响应200,并为部署的链码返回哈希值。



但是之后,我在docker日志中收到以下错误:

  08:44:26.560 [consensus / noops] processTransactions  - > DEBU 053启动具有时间戳的TX批次:秒:1473929066 nanos:560229743 
08:44:26.560 [consensus / noops] processTransactions - > DEBU 054使用时间戳秒执行1个事务的批次:1473929066 nanos:560229743
08:44:26.563 [chaincode] getArgsAndEnv - > DEBU 055可执行文件是/ opt / gopath / bin / 1e90b51f9129b97d5312d5c24364085777602a06d40d6e2c9209b4f30d7e66facb26e956443028611539962acc6de550eba03bbb1fd0e7bbd655cb19c5a6ef84
08:44:26.564 [chaincode]部署 - > DEBU 056部署链码1e90b51f9129b97d5312d5c24364085777602a06d40d6e2c9209b4f30d7e66facb26e956443028611539962acc6de550eba03bbb1fd0e7bbd655cb19c5a6ef84(networkid:dev,peerid:vp0)
08:44:26.564 [container] lockContainer - > DEBU 057等待容器(dev-vp0-1e90b51f9129b97d5312d5c24364085777602a06d40d6e2c9209b4f30d7e66facb26e956443028611539962acc6de550eba03bbb1fd0e7bbd655cb19c5a6ef84)lock
08:44:26.564 [container] lockContainer - > DEBU 058获取容器(dev-vp0-1e90b51f9129b97d5312d5c24364085777602a06d40d6e2c9209b4f30d7e66facb26e956443028611539962acc6de550eba03bbb1fd0e7bbd655cb19c5a6ef84)lock

** 08:44:26.565 [dockercontroller] deployImage - > ERRO 059构建图像时出错:无法连接到Docker端点**

那么我该如何解决? / p>

另一个更新。我做了以下:



1)编辑/ etc / default / docker添加条目:DOCKER_OPTS = - api-cors-header ='*'-H tcp://0.0.0.0:2375 -H unix:///var/run/docker.sock



2)重新启动的码头服务器



3)使用docker-compose up命令启动节点



尝试部署链码,现在我收到一个不同的错误:

  vp0_1 | 06:09:33.441 [consensus / noops] handleChannels  - > DEBU 048由于时间
vp0_1 |处理块06:09:33.441 [consensus / noops] processTransactions - > DEBU 049启动TX批次与时间戳:秒:1475042973 nanos:441383619
vp0_1 | 06:09:33.441 [consensus / noops] processTransactions - > DEBU 04a使用时间戳秒执行1个交易的批次:1475042973 nanos:441383619
vp0_1 | 06:09:33.446 [chaincode] getArgsAndEnv - > DEBU 04b可执行文件是/ opt / gopath / bin / 1e90b51f9129b97d5312d5c24364085777602a06d40d6e2c9209b4f30d7e66facb26e956443028611539962acc6de550eba03bbb1fd0e7bbd655cb19c5a6ef84
vp0_1 | 06:09:33.446 [chaincode]部署 - > DEBU 04c部署链码1e90b51f9129b97d5312d5c24364085777602a06d40d6e2c9209b4f30d7e66facb26e956443028611539962acc6de550eba03bbb1fd0e7bbd655cb19c5a6ef84(networkid:dev,peerid:vp0)
vp0_1 | 06:09:33.446 [container] lockContainer - > DEBU 04d等待容器(dev-vp0-1e90b51f9129b97d5312d5c24364085777602a06d40d6e2c9209b4f30d7e66facb26e956443028611539962acc6de550eba03bbb1fd0e7bbd655cb19c5a6ef84)lock
vp0_1 | 06:09:33.446 [container] lockContainer - > DEBU 04e得到容器(dev-vp0-1e90b51f9129b97d5312d5c24364085777602a06d40d6e2c9209b4f30d7e66facb26e956443028611539962acc6de550eba03bbb1fd0e7bbd655cb19c5a6ef84)lock
vp0_1 | 06:09:37.608 [对等]确保连接 - > DEBU 04f触摸服务指示没有丢弃的连接
vp0_1 | 06:09:37.608 [对等]确保连接 - > DEBU 050连接到:[] vp0_1 | 06:09:37.608 [对等]确保连接 - > DEBU 051发现知道:[]
vp0_1 | 06:09:39.533 [dockercontroller] deployImage - > ERRO 052构建图像时出现错误:最新版本未找到存储库docker.io/hyperledger/fabric-baseimage
vp0_1 | 06:09:39.533 [dockercontroller] deployImage - > ERRO 053图像输出:


解决方案

您是否检查了您的容器环境变量:

  CORE_VM_ENDPOINT = unix:///var/run/docker.sock 

确保这个文件可以从您的容器中访问,因为某些原因我不是这样,我不得不挂载它。 >

然后如果你得到 deployImage - > ERRO 052构建图像时出错:最新的标签未找到.. 。这是一个已知的问题(例如错误构建图像:标记最新在仓库中找不到docker.io/hyperledger/fabric-baseimage )。



我下载了一个可用的图像并将其重新添加

  docker pull hyperledger / fabric-baseimage:x86_64-0.1.0 
docker tag hyperledger / fabric-baseimage:x86_64 -0.1.0 hyperledger / fabric-baseimage:最新


I have setup a 2 node Hyperledger network using Docker images on Ubuntu 14.04 by creating 2 containers as per the steps provided @ http://hyperledger-fabric.readthedocs.io/en/latest/Setup/Network-setup/#leveraging-published-docker-images

Then I tried to deploy a chaincode, which compiles without errors, by calling POST /chaincode API and got response 200 with the hash returned for the deployed chaincode.

But immediately after that I got the following error in the docker logs:

08:44:26.560 [consensus/noops] processTransactions -> DEBU 053 Starting TX batch with timestamp: seconds:1473929066 nanos:560229743
08:44:26.560 [consensus/noops] processTransactions -> DEBU 054 Executing batch of 1 transactions with timestamp seconds:1473929066 nanos:560229743
08:44:26.563 [chaincode] getArgsAndEnv -> DEBU 055 Executable is /opt/gopath/bin/1e90b51f9129b97d5312d5c24364085777602a06d40d6e2c9209b4f30d7e66facb26e956443028611539962acc6de550eba03bbb1fd0e7bbd655cb19c5a6ef84
08:44:26.564 [chaincode] Deploy -> DEBU 056 deploying chaincode 1e90b51f9129b97d5312d5c24364085777602a06d40d6e2c9209b4f30d7e66facb26e956443028611539962acc6de550eba03bbb1fd0e7bbd655cb19c5a6ef84(networkid:dev,peerid:vp0)
08:44:26.564 [container] lockContainer -> DEBU 057 waiting for container(dev-vp0-1e90b51f9129b97d5312d5c24364085777602a06d40d6e2c9209b4f30d7e66facb26e956443028611539962acc6de550eba03bbb1fd0e7bbd655cb19c5a6ef84) lock
08:44:26.564 [container] lockContainer -> DEBU 058 got container (dev-vp0-1e90b51f9129b97d5312d5c24364085777602a06d40d6e2c9209b4f30d7e66facb26e956443028611539962acc6de550eba03bbb1fd0e7bbd655cb19c5a6ef84) lock

**08:44:26.565 [dockercontroller] deployImage -> ERRO 059 Error building images: cannot connect to Docker endpoint**

So how do I resolve this?

Another update. I did the following:

1) Edited /etc/default/docker to add the entry: DOCKER_OPTS="--api-cors-header='*' -H tcp://0.0.0.0:2375 -H unix:///var/run/docker.sock "

2) Restarted docker

3) Started a node using docker-compose up command

Tried deploying chaincode and now I get a different error:

    vp0_1 | 06:09:33.441 [consensus/noops] handleChannels -> DEBU 048 Process block due to time 
    vp0_1 | 06:09:33.441 [consensus/noops] processTransactions -> DEBU 049 Starting TX batch with timestamp: seconds:1475042973 nanos:441383619 
    vp0_1 | 06:09:33.441 [consensus/noops] processTransactions -> DEBU 04a Executing batch of 1 transactions with timestamp seconds:1475042973 nanos:441383619 
    vp0_1 | 06:09:33.446 [chaincode] getArgsAndEnv -> DEBU 04b Executable is /opt/gopath/bin/1e90b51f9129b97d5312d5c24364085777602a06d40d6e2c9209b4f30d7e66facb26e956443028611539962acc6de550eba03bbb1fd0e7bbd655cb19c5a6ef84 
    vp0_1 | 06:09:33.446 [chaincode] Deploy -> DEBU 04c deploying chaincode 1e90b51f9129b97d5312d5c24364085777602a06d40d6e2c9209b4f30d7e66facb26e956443028611539962acc6de550eba03bbb1fd0e7bbd655cb19c5a6ef84(networkid:dev,peerid:vp0) 
    vp0_1 | 06:09:33.446 [container] lockContainer -> DEBU 04d waiting for container(dev-vp0-1e90b51f9129b97d5312d5c24364085777602a06d40d6e2c9209b4f30d7e66facb26e956443028611539962acc6de550eba03bbb1fd0e7bbd655cb19c5a6ef84) lock 
    vp0_1 | 06:09:33.446 [container] lockContainer -> DEBU 04e got container (dev-vp0-1e90b51f9129b97d5312d5c24364085777602a06d40d6e2c9209b4f30d7e66facb26e956443028611539962acc6de550eba03bbb1fd0e7bbd655cb19c5a6ef84) lock 
    vp0_1 | 06:09:37.608 [peer] ensureConnected -> DEBU 04f Touch service indicates no dropped connections 
    vp0_1 | 06:09:37.608 [peer] ensureConnected -> DEBU 050 Connected to: [] vp0_1 | 06:09:37.608 [peer] ensureConnected -> DEBU 051 Discovery knows about: [] 
    vp0_1 | 06:09:39.533 [dockercontroller] deployImage -> ERRO 052 Error building images: Tag latest not found in repository docker.io/hyperledger/fabric-baseimage 
    vp0_1 | 06:09:39.533 [dockercontroller] deployImage -> ERRO 053 Image Output:

解决方案

Did you check your container environment variable:

CORE_VM_ENDPOINT=unix:///var/run/docker.sock

Make sure this file is accessible from within your container as for some reason it was not the case for me and I had to mount it.

Then if you get deployImage -> ERRO 052 Error building images: Tag latest not found... it is a known issue (ex. Error building images: Tag latest not found in repository docker.io/hyperledger/fabric-baseimage).

I downloaded one of the available images and retagged it

docker pull hyperledger/fabric-baseimage:x86_64-0.1.0
docker tag hyperledger/fabric-baseimage:x86_64-0.1.0 hyperledger/fabric-baseimage:latest

这篇关于未找到Hyperledger Docker端点的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆