尝试更新hyperledger-composer版本,但仍与客户端版本不兼容

时间:2017-08-31 07:42:03

标签: hyperledger-composer

我只是Hyperledger Composer的新手。所以我尝试按照本指南使用Docker部署REST服务器

Deploying the REST server for a business network

然后当我运行docker时,它会在docker logs

上显示此错误
docker logs rest
0|composer | WARNING: NODE_APP_INSTANCE value of '0' did not match any instance config file names.
0|composer | WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode
0|composer | Discovering types from business network definition ...
0|composer | D0831 07:04:36.180952003      24 env_linux.c:66]             Warning: insecure environment read function 'getenv' used
0|composer | D0831 07:04:37.574385287      24 env_linux.c:66]             Warning: insecure environment read function 'getenv' used
0|composer | Connection fails: Error: Error trying to ping. Error: Composer runtime (0.11.3) is not compatible with client (0.11.2)
0|composer | It will be retried for the next request.
0|composer | Exception: Error: Error trying to ping. Error: Composer runtime (0.11.3) is not compatible with client (0.11.2)
0|composer | Error: Error trying to ping. Error: Composer runtime (0.11.3) is not compatible with client (0.11.2)
0|composer |     at _checkRuntimeVersions.then.catch (/usr/local/lib/node_modules/composer-rest-server/node_modules/composer-connector-hlfv1/lib/hlfconnection.js:696:34)
PM2        | App [composer-rest-server] with id [0] and pid [24], exited with code [1] via signal [SIGINT]
PM2        | Starting execution sequence in -fork mode- for app name:composer-rest-server id:0
PM2        | App name:composer-rest-server id:0 online

所以我尝试按照同一文档上的本指南更新版本

Updating Hyperledger Composer

但是在我停止/重新启动结构后,再次重新部署链代码并运行docker时,错误仍然存​​在。

任何人都可以告诉我我错过了什么吗?

注意:我也尝试this solution,但仍然遇到同样的问题。

1 个答案:

答案 0 :(得分:2)

好的,我已经解决了这个问题。我删除所有的docker镜像并启动新的结构再次下载图像,它可以工作!!

docker rmi $(docker images  -q)