Hyperledger fabric 尝试在Hyperledger结构上实例化链码时出错_Hyperledger Fabric_Hyperledger

Hyperledger fabric 尝试在Hyperledger结构上实例化链码时出错

hyperledger-fabric

Hyperledger fabric 尝试在Hyperledger结构上实例化链码时出错,hyperledger-fabric,hyperledger,Hyperledger Fabric,Hyperledger,我试图根据此处描述的规范创建自定义业务网络：我为org1.example.com创建了5个对等点，为org2.example.com创建了一个对等点我可以在peer0.org1.example.com上使用docker cli启动网络并安装链码，但当我尝试实例化它时，我遇到以下错误：错误：错误背书链码：rpc错误：代码=未知描述= 启动容器时出错：API错误（404）：{“消息”：“网络”\u byfn 找不到“} 以下是业务网络记录器的输出： peer0.org1.example.com

我试图根据此处描述的规范创建自定义业务网络：

我为org1.example.com创建了5个对等点，为org2.example.com创建了一个对等点

我可以在peer0.org1.example.com上使用docker cli启动网络并安装链码，但当我尝试实例化它时，我遇到以下错误：

错误：错误背书链码：rpc错误：代码=未知描述= 启动容器时出错：API错误（404）：{“消息”：“网络”\u byfn 找不到“}

以下是业务网络记录器的输出：

peer0.org1.example.com    | 2017-10-16 15:59:20.826 UTC [ccprovider] NewCCContext -> DEBU 3c1 NewCCCC (chain=c1,chaincode=mycc,version=1.0,txid=cc0e1367388a59a5186343adc6d4e526004728c73d53070e794d9f663e704795,syscc=false,proposal=0xc421b9fea0,canname=mycc:1.0
peer0.org1.example.com    | 2017-10-16 15:59:20.826 UTC [chaincode] Launch -> DEBU 3c2 launchAndWaitForRegister fetched 2411 bytes from file system
peer0.org1.example.com    | 2017-10-16 15:59:20.826 UTC [chaincode] launchAndWaitForRegister -> DEBU 3c3 chaincode mycc:1.0 is being launched
peer0.org1.example.com    | 2017-10-16 15:59:20.826 UTC [chaincode] getArgsAndEnv -> DEBU 3c4 Executable is chaincode
peer0.org1.example.com    | 2017-10-16 15:59:20.826 UTC [chaincode] getArgsAndEnv -> DEBU 3c5 Args [chaincode -peer.address=peer0.org1.example.com:7051]
peer0.org1.example.com    | 2017-10-16 15:59:20.827 UTC [chaincode] launchAndWaitForRegister -> DEBU 3c6 start container: mycc:1.0(networkid:dev,peerid:peer0.org1.example.com)
peer0.org1.example.com    | 2017-10-16 15:59:20.827 UTC [chaincode] launchAndWaitForRegister -> DEBU 3c7 start container with args: chaincode -peer.address=peer0.org1.example.com:7051
peer0.org1.example.com    | 2017-10-16 15:59:20.827 UTC [chaincode] launchAndWaitForRegister -> DEBU 3c8 start container with env:
peer0.org1.example.com    |     CORE_CHAINCODE_ID_NAME=mycc:1.0
peer0.org1.example.com    |     CORE_PEER_TLS_ENABLED=true
peer0.org1.example.com    |     CORE_CHAINCODE_LOGGING_LEVEL=info
peer0.org1.example.com    |     CORE_CHAINCODE_LOGGING_SHIM=warning
peer0.org1.example.com    |     CORE_CHAINCODE_LOGGING_FORMAT=%{color}%{time:2006-01-02 15:04:05.000 MST} [%{module}] %{shortfunc} -> %{level:.4s} %{id:03x}%{color:reset} %{message}
peer0.org1.example.com    | 2017-10-16 15:59:20.827 UTC [container] lockContainer -> DEBU 3c9 waiting for container(dev-peer0.org1.example.com-mycc-1.0) lock
peer0.org1.example.com    | 2017-10-16 15:59:20.827 UTC [container] lockContainer -> DEBU 3ca got container (dev-peer0.org1.example.com-mycc-1.0) lock
peer0.org1.example.com    | 2017-10-16 15:59:20.827 UTC [dockercontroller] Start -> DEBU 3cb Cleanup container dev-peer0.org1.example.com-mycc-1.0
peer0.org1.example.com    | 2017-10-16 15:59:20.832 UTC [dockercontroller] stopInternal -> DEBU 3cc Stop container dev-peer0.org1.example.com-mycc-1.0(No such container: dev-peer0.org1.example.com-mycc-1.0)
peer0.org1.example.com    | 2017-10-16 15:59:20.834 UTC [dockercontroller] stopInternal -> DEBU 3cd Kill container dev-peer0.org1.example.com-mycc-1.0 (No such container: dev-peer0.org1.example.com-mycc-1.0)
peer0.org1.example.com    | 2017-10-16 15:59:20.835 UTC [dockercontroller] stopInternal -> DEBU 3ce Remove container dev-peer0.org1.example.com-mycc-1.0 (No such container: dev-peer0.org1.example.com-mycc-1.0)
peer0.org1.example.com    | 2017-10-16 15:59:20.836 UTC [dockercontroller] Start -> DEBU 3cf Start container dev-peer0.org1.example.com-mycc-1.0
peer0.org1.example.com    | 2017-10-16 15:59:20.836 UTC [dockercontroller] getDockerHostConfig -> DEBU 3d0 docker container hostconfig NetworkMode: _byfn
peer0.org1.example.com    | 2017-10-16 15:59:20.836 UTC [dockercontroller] createContainer -> DEBU 3d1 Create container: dev-peer0.org1.example.com-mycc-1.0
peer0.org1.example.com    | 2017-10-16 15:59:20.844 UTC [dockercontroller] Start -> DEBU 3d2 start-could not find image <dev-peer0.org1.example.com-mycc-1.0-384f11f484b9302df90b453200cfb25174305fce8f53f4e94d45ee3b6cab0ce9> (container id <dev-peer0.org1.example.com-mycc-1.0>), because of <no such image>...attempt to recreate image
peer0.org1.example.com    | 2017-10-16 15:59:20.844 UTC [chaincode-platform] generateDockerfile -> DEBU 3d3 
peer0.org1.example.com    | FROM hyperledger/fabric-baseos:x86_64-0.3.2
peer0.org1.example.com    | ADD binpackage.tar /usr/local/bin
peer0.org1.example.com    | LABEL org.hyperledger.fabric.chaincode.id.name="mycc" \
peer0.org1.example.com    |       org.hyperledger.fabric.chaincode.id.version="1.0" \
peer0.org1.example.com    |       org.hyperledger.fabric.chaincode.type="GOLANG" \
peer0.org1.example.com    |       org.hyperledger.fabric.version="1.0.2" \
peer0.org1.example.com    |       org.hyperledger.fabric.base.version="0.3.2"
peer0.org1.example.com    | ENV CORE_CHAINCODE_BUILDLEVEL=1.0.2
peer0.org1.example.com    | ENV CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/peer.crt
peer0.org1.example.com    | COPY peer.crt /etc/hyperledger/fabric/peer.crt
peer0.org1.example.com    | 2017-10-16 15:59:20.846 UTC [util] DockerBuild -> DEBU 3d4 Attempting build with image hyperledger/fabric-ccenv:x86_64-1.0.2
peer0.org1.example.com    | 2017-10-16 15:59:46.596 UTC [dockercontroller] deployImage -> DEBU 3d5 Created image: dev-peer0.org1.example.com-mycc-1.0-384f11f484b9302df90b453200cfb25174305fce8f53f4e94d45ee3b6cab0ce9
peer0.org1.example.com    | 2017-10-16 15:59:46.596 UTC [dockercontroller] Start -> DEBU 3d6 start-recreated image successfully
peer0.org1.example.com    | 2017-10-16 15:59:46.596 UTC [dockercontroller] createContainer -> DEBU 3d7 Create container: dev-peer0.org1.example.com-mycc-1.0
peer0.org1.example.com    | 2017-10-16 15:59:46.664 UTC [dockercontroller] createContainer -> DEBU 3d8 Created container: dev-peer0.org1.example.com-mycc-1.0-384f11f484b9302df90b453200cfb25174305fce8f53f4e94d45ee3b6cab0ce9
peer0.org1.example.com    | 2017-10-16 15:59:46.745 UTC [dockercontroller] Start -> ERRO 3d9 start-could not start container: API error (404): {"message":"network _byfn not found"}
peer0.org1.example.com    | 2017-10-16 15:59:46.745 UTC [container] unlockContainer -> DEBU 3da container lock deleted(dev-peer0.org1.example.com-mycc-1.0)
peer0.org1.example.com    | 2017-10-16 15:59:46.745 UTC [chaincode] func1 -> DEBU 3db chaincode mycc:1.0 launch seq completed
peer0.org1.example.com    | 2017-10-16 15:59:46.745 UTC [chaincode] **Launch -> ERRO 3dc launchAndWaitForRegister failed Error starting container: API error (404): {"message":"network _byfn not found"}**
peer0.org1.example.com    | 2017-10-16 15:59:46.745 UTC [endorser] callChaincode -> DEBU 3dd Exit
peer0.org1.example.com    | 2017-10-16 15:59:46.745 UTC [endorser] simulateProposal -> ERRO 3de failed to invoke chaincode name:"lscc"  on transaction cc0e1367388a59a5186343adc6d4e526004728c73d53070e794d9f663e704795, error: Error starting container: API error (404): {"message":"network _byfn not found"}
peer0.org1.example.com    | 2017-10-16 15:59:46.745 UTC [endorser] simulateProposal -> DEBU 3df Exit
peer0.org1.example.com    | 2017-10-16 15:59:46.745 UTC [lockbasedtxmgr] Done -> DEBU 3e0 Done with transaction simulation / query execution [1a086ccc-1882-413a-a679-047b8478fae0]
peer0.org1.example.com    | 2017-10-16 15:59:46.745 UTC [endorser] ProcessProposal -> DEBU 3e1 Exit
orderer.example.com       | 2017-10-16 15:59:46.748 UTC [orderer/common/broadcast] Handle -> WARN 8de Error reading from stream: rpc error: code = Canceled desc = context canceled
orderer.example.com       | 2017-10-16 15:59:46.748 UTC [orderer/main] func1 -> DEBU 8df Closing Broadcast stream
^Fpeer0.org1.example.com    | 2017-10-16 16:04:03.628 UTC [endorser] ProcessProposal -> DEBU 3e2 Entry
peer0.org1.example.com    | 2017-10-16 16:04:03.628 UTC [protoutils] ValidateProposalMessage -> DEBU 3e3 ValidateProposalMessage starts for signed proposal 0xc4218fa060
peer0.org1.example.com    | 2017-10-16 16:04:03.628 UTC [protoutils] validateChannelHeader -> DEBU 3e4 validateChannelHeader info: header type 3
peer0.org1.example.com    | 2017-10-16 16:04:03.628 UTC [protoutils] checkSignatureFromCreator -> DEBU 3e5 checkSignatureFromCreator starts
peer0.org1.example.com    | 2017-10-16 16:04:03.629 UTC [protoutils] checkSignatureFromCreator -> DEBU 3e6 checkSignatureFromCreator info: creator is &{Org1MSP 3cd83aa899c76517d9acd559d130c87e9c8bc4ca893f4116d7dbc85b14b734d3}
peer0.org1.example.com    | 2017-10-16 16:04:03.629 UTC [protoutils] checkSignatureFromCreator -> DEBU 3e7 checkSignatureFromCreator info: creator is valid
peer0.org1.example.com    | 2017-10-16 16:04:03.629 UTC [protoutils] checkSignatureFromCreator -> DEBU 3e8 checkSignatureFromCreator exists successfully
peer0.org1.example.com    | 2017-10-16 16:04:03.629 UTC [protoutils] validateChaincodeProposalMessage -> DEBU 3e9 validateChaincodeProposalMessage starts for proposal 0xc421d14aa0, header 0xc4218fa090
peer0.org1.example.com    | 2017-10-16 16:04:03.629 UTC [protoutils] validateChaincodeProposalMessage -> DEBU 3ea validateChaincodeProposalMessage info: header extension references chaincode name:"mycc" 
peer0.org1.example.com    | 2017-10-16 16:04:03.629 UTC [endorser] ProcessProposal -> DEBU 3eb processing txid: 854682493d27b8613c504f0780f750520367f328a63526516191727f33a355eb
peer0.org1.example.com    | 2017-10-16 16:04:03.629 UTC [fsblkstorage] retrieveTransactionByID -> DEBU 3ec retrieveTransactionByID() - txId = [854682493d27b8613c504f0780f750520367f328a63526516191727f33a355eb]
peer0.org1.example.com    | 2017-10-16 16:04:03.630 UTC [lockbasedtxmgr] NewTxSimulator -> DEBU 3ed constructing new tx simulator
peer0.org1.example.com    | 2017-10-16 16:04:03.630 UTC [lockbasedtxmgr] newLockBasedTxSimulator -> DEBU 3ee constructing new tx simulator [18598d15-803e-4ca0-87dd-6da03d90c9a8]
peer0.org1.example.com    | 2017-10-16 16:04:03.630 UTC [endorser] simulateProposal -> DEBU 3ef Entry - txid: 854682493d27b8613c504f0780f750520367f328a63526516191727f33a355eb channel id: c1
peer0.org1.example.com    | 2017-10-16 16:04:03.630 UTC [ccprovider] NewCCContext -> DEBU 3f0 NewCCCC (chain=c1,chaincode=lscc,version=1.0.2,txid=854682493d27b8613c504f0780f750520367f328a63526516191727f33a355eb,syscc=true,proposal=0xc421d14aa0,canname=lscc:1.0.2
peer0.org1.example.com    | 2017-10-16 16:04:03.630 UTC [chaincode] Launch -> DEBU 3f1 chaincode is running(no need to launch) : lscc:1.0.2
peer0.org1.example.com    | 2017-10-16 16:04:03.630 UTC [chaincode] Execute -> DEBU 3f2 Entry
peer0.org1.example.com    | 2017-10-16 16:04:03.630 UTC [chaincode] Execute -> DEBU 3f3 chaincode canonical name: lscc:1.0.2
peer0.org1.example.com    | 2017-10-16 16:04:03.630 UTC [chaincode] sendExecuteMessage -> DEBU 3f4 [85468249]Inside sendExecuteMessage. Message TRANSACTION
peer0.org1.example.com    | 2017-10-16 16:04:03.630 UTC [chaincode] setChaincodeProposal -> DEBU 3f5 Setting chaincode proposal context...
peer0.org1.example.com    | 2017-10-16 16:04:03.630 UTC [chaincode] setChaincodeProposal -> DEBU 3f6 Proposal different from nil. Creating chaincode proposal context...
peer0.org1.example.com    | 2017-10-16 16:04:03.630 UTC [chaincode] sendExecuteMessage -> DEBU 3f7 [85468249]sendExecuteMsg trigger event TRANSACTION
peer0.org1.example.com    | 2017-10-16 16:04:03.630 UTC [chaincode] processStream -> DEBU 3f8 [85468249]Move state message TRANSACTION
peer0.org1.example.com    | 2017-10-16 16:04:03.630 UTC [chaincode] HandleMessage -> DEBU 3f9 [85468249]Fabric side Handling ChaincodeMessage of type: TRANSACTION in state ready
peer0.org1.example.com    | 2017-10-16 16:04:03.630 UTC [chaincode] filterError -> DEBU 3fa Ignoring NoTransitionError: no transition
peer0.org1.example.com    | 2017-10-16 16:04:03.630 UTC [chaincode] processStream -> DEBU 3fb [85468249]sending state message TRANSACTION
peer0.org1.example.com    | 2017-10-16 16:04:03.630 UTC [shim] func1 -> DEBU 3fc [85468249]Received message TRANSACTION from shim
peer0.org1.example.com    | 2017-10-16 16:04:03.630 UTC [shim] handleMessage -> DEBU 3fd [85468249]Handling ChaincodeMessage of type: TRANSACTION(state:ready)
peer0.org1.example.com    | 2017-10-16 16:04:03.630 UTC [shim] beforeTransaction -> DEBU 3fe [85468249]Received TRANSACTION, invoking transaction on chaincode(Src:ready, Dst:ready)
peer0.org1.example.com    | 2017-10-16 16:04:03.631 UTC [shim] handleGetState -> DEBU 3ff [85468249]Sending GET_STATE
peer0.org1.example.com    | 2017-10-16 16:04:03.631 UTC [chaincode] processStream -> DEBU 400 [85468249]Received message GET_STATE from shim
peer0.org1.example.com    | 2017-10-16 16:04:03.631 UTC [chaincode] HandleMessage -> DEBU 401 [85468249]Fabric side Handling ChaincodeMessage of type: GET_STATE in state ready
peer0.org1.example.com    | 2017-10-16 16:04:03.631 UTC [chaincode] afterGetState -> DEBU 402 [85468249]Received GET_STATE, invoking get state from ledger
peer0.org1.example.com    | 2017-10-16 16:04:03.631 UTC [chaincode] filterError -> DEBU 403 Ignoring NoTransitionError: no transition
peer0.org1.example.com    | 2017-10-16 16:04:03.631 UTC [chaincode] func1 -> DEBU 404 [85468249] getting state for chaincode lscc, key mycc, channel c1
peer0.org1.example.com    | 2017-10-16 16:04:03.631 UTC [statecouchdb] GetState -> DEBU 405 GetState(). ns=lscc, key=mycc
peer0.org1.example.com    | 2017-10-16 16:04:03.631 UTC [couchdb] ReadDoc -> DEBU 406 Entering ReadDoc()  id=[lsccmycc]
peer0.org1.example.com    | 2017-10-16 16:04:03.631 UTC [couchdb] handleRequest -> DEBU 407 Entering handleRequest()  method=GET  url=http://couchdb0:5984/c1/lscc%00mycc?attachments=true
peer0.org1.example.com    | 2017-10-16 16:04:03.632 UTC [couchdb] handleRequest -> DEBU 408 HTTP Request: GET /c1/lscc%00mycc?attachments=true HTTP/1.1 | Host: couchdb0:5984 | User-Agent: Go-http-client/1.1 | Accept: multipart/related | Accept-Encoding: gzip |  | 
peer0.org1.example.com    | 2017-10-16 16:04:03.634 UTC [couchdb] handleRequest -> DEBU 409 Couch DB Error:not_found,  Status Code:404,  Reason:missing
peer0.org1.example.com    | 2017-10-16 16:04:03.634 UTC [couchdb] ReadDoc -> DEBU 40a Document not found (404), returning nil value instead of 404 error
peer0.org1.example.com    | 2017-10-16 16:04:03.634 UTC [chaincode] func1 -> DEBU 40b [85468249]No state associated with key: mycc. Sending RESPONSE with an empty payload
peer0.org1.example.com    | 2017-10-16 16:04:03.634 UTC [chaincode] 1 -> DEBU 40c [85468249]handleGetState serial send RESPONSE
peer0.org1.example.com    | 2017-10-16 16:04:03.634 UTC [shim] func1 -> DEBU 40d [85468249]Received message RESPONSE from shim
peer0.org1.example.com    | 2017-10-16 16:04:03.634 UTC [shim] handleMessage -> DEBU 40e [85468249]Handling ChaincodeMessage of type: RESPONSE(state:ready)
peer0.org1.example.com    | 2017-10-16 16:04:03.635 UTC [shim] sendChannel -> DEBU 40f [85468249]before send
peer0.org1.example.com    | 2017-10-16 16:04:03.635 UTC [shim] sendChannel -> DEBU 410 [85468249]after send
peer0.org1.example.com    | 2017-10-16 16:04:03.635 UTC [shim] afterResponse -> DEBU 411 [85468249]Received RESPONSE, communicated (state:ready)
peer0.org1.example.com    | 2017-10-16 16:04:03.635 UTC [shim] handleGetState -> DEBU 412 [85468249]GetState received payload RESPONSE
peer0.org1.example.com    | 2017-10-16 16:04:03.635 UTC [lscc] Invoke -> ERRO 413 error getting chaincode mycc on channel: c1(err:could not find chaincode with name 'mycc')
peer0.org1.example.com    | 2017-10-16 16:04:03.635 UTC [shim] func1 -> DEBU 414 [85468249]Transaction completed. Sending COMPLETED
peer0.org1.example.com    | 2017-10-16 16:04:03.635 UTC [shim] func1 -> DEBU 415 [85468249]Move state message COMPLETED
peer0.org1.example.com    | 2017-10-16 16:04:03.635 UTC [shim] handleMessage -> DEBU 416 [85468249]Handling ChaincodeMessage of type: COMPLETED(state:ready)
peer0.org1.example.com    | 2017-10-16 16:04:03.635 UTC [shim] func1 -> DEBU 417 [85468249]send state message COMPLETED
peer0.org1.example.com    | 2017-10-16 16:04:03.635 UTC [chaincode] processStream -> DEBU 418 [85468249]Received message COMPLETED from shim
peer0.org1.example.com    | 2017-10-16 16:04:03.635 UTC [chaincode] HandleMessage -> DEBU 419 [85468249]Fabric side Handling ChaincodeMessage of type: COMPLETED in state ready
peer0.org1.example.com    | 2017-10-16 16:04:03.635 UTC [chaincode] HandleMessage -> DEBU 41a [854682493d27b8613c504f0780f750520367f328a63526516191727f33a355eb]HandleMessage- COMPLETED. Notify
peer0.org1.example.com    | 2017-10-16 16:04:03.635 UTC [chaincode] notify -> DEBU 41b notifying Txid:854682493d27b8613c504f0780f750520367f328a63526516191727f33a355eb
peer0.org1.example.com    | 2017-10-16 16:04:03.635 UTC [chaincode] Execute -> DEBU 41c Exit
peer0.org1.example.com    | 2017-10-16 16:04:03.635 UTC [endorser] simulateProposal -> DEBU 41d Exit
peer0.org1.example.com    | 2017-10-16 16:04:03.635 UTC [lockbasedtxmgr] Done -> DEBU 41e Done with transaction simulation / query execution [18598d15-803e-4ca0-87dd-6da03d90c9a8]
peer0.org1.example.com    | 2017-10-16 16:04:03.635 UTC [endorser] ProcessProposal -> DEBU 41f Exit

编辑3：

peer0.org1.example.com    | 2017-10-17 15:37:48.352 UTC [chaincode] Launch -> ERRO 52f launchAndWaitForRegister failed Timeout expired while starting chaincode mycc:1.0(networkid:dev,peerid:peer0.org1.example.com,tx:21de5c78faf2938ec4d64f3c3deb762bd20e56187921dddb895e8f4e1ced220f)
peer0.org1.example.com    | 2017-10-17 15:37:48.352 UTC [endorser] callChaincode -> DEBU 530 Exit
peer0.org1.example.com    | 2017-10-17 15:37:48.352 UTC [endorser] simulateProposal -> ERRO 531 failed to invoke chaincode name:"lscc"  on transaction 21de5c78faf2938ec4d64f3c3deb762bd20e56187921dddb895e8f4e1ced220f, error: Timeout expired while starting chaincode mycc:1.0(networkid:dev,peerid:peer0.org1.example.com,tx:21de5c78faf2938ec4d64f3c3deb762bd20e56187921dddb895e8f4e1ced220f)

通过检查您提供的日志文件中的错误：

peer0.org1.example.com | 2017-10-16 15:59:46.745 UTC[dockercontroller]启动->ERRO 3d9启动无法启动容器：API错误（404）：{“消息”：“未找到网络”}

网络名称似乎有意外的空格字符

network\u byfn

，因此我猜您需要在

docker compose.yaml

文件中修复它：

检查

CORE\u VM\u DOCKER\u HOSTCONFIG\u NETWORKMODE

环境变量的值，可以在以下位置找到它：

您还可以检查文件内容，通常假定为：

COMPOSE_PROJECT_NAME=net

因此，这里的问题是COMPOSE_项目名称env。当我尝试从具有网络规范的文件夹中启动网络时，由于某种原因，该环境仍然为空，并且出现上述错误。当我将网络规范复制到/fabric samples/firtst网络文件夹并尝试再次启动时，COMPOSE_PROJECT_名称设置为“net”值，一切正常。此外，当我尝试在/base/peer-base.yaml中将此值硬编码为“net”并尝试从默认文件夹再次启动网络时，我会在peer上得到超时错误

编辑1：

最后的答案是：我没有为前面提到的env设置.env文件。文件夹中的变量。

当我设置

COMPOSE\u PROJECT\u NAME=block\u chain时，我也会遇到类似的错误：
Error: Error endorsing chaincode: rpc error: code = Unknown desc = error starting container: 
API error (404): {"message":"network block_chain_network not found"}

但该网络实际上是以区块链\u network
的名称创建的。因此，它在我的情况下不起作用
 CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=xxx_yyy 


我的观察：COMPOSE\u PROJECT\u NAME
不接受任何特殊字符。在此之后，我可以通过设置COMPOSE\u PROJECT\u NAME=blockchain
成功实例化链码
希望这对其他可能遇到同样问题的人有所帮助。
当我开始工作时，我意识到还有一件更重要的事情，那就是，您在docker-compose-cli.yaml中给出的网络名称是“mySensortium”
必须匹配peer-base.yaml中的值作为核心\u VM\u DOCKER\u HOSTCONFIG\u NETWORKMODE=${COMPOSE\u PROJECT\u NAME}\u myconsortium
SCRIPTS似乎正在做的是，将我们在cli.yaml中指定的网络名称作为${COMPOSE_PROJECT_name}的env变量，并将其作为${COMPOSE_PROJECT_name}
在我定义的.env
文件中
COMPOSE_PROJECT_NAME=xxx

在docker-compose.yml文件中
version: '2'

networks:
  yyy:   <----------------

services:
 ...
 ...
    - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=zzz
 ...
 ...

列出docker networks（docker network ls
）表明，创建了名为xxx\u yyy
的网络，因此基本上将CORE\u VM\u docker\u HOSTCONFIG\u NETWORKMODE
的值更改为xxx\u yyy
解决了我的问题
 CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=xxx_yyy 


在我的例子中，我可以通过将.env
文件移动到与docker compose.yaml
文件相同的目录来解决这个问题。您需要共享的不仅仅是日志。您可以共享用于创建此网络的docker compose文件吗？另外，您是否修改了scripts/script.sh以使其适应您创建的配置？如果是这样的话，也请分享。@christo4ferris Tnx获得答案。请看我的编辑。同样关于script.sh：我已经在docker-compse-cli.yaml文件中注释了启动它的行。我只是手动生成所有加密和其他人工制品，并使用CLI创建通道、加入对等通道并将链码安装到通道。@christo4ferris我已经添加了您建议的内容，但似乎我们对COMPOSE_PROJECT_名称有问题（如下面回答中Artem Barger所建议的）peer-base.yaml文件中引用的env。当我在peer0.org0.example.com中回显它时，我得到的是空的响应。@christo4ferris这个问题有任何更新吗？答案是Tnx。就我看来，关于你建议的事情，一切都很好。你能看到我的更新吗？你能添加.env文件的内容吗？为peer0.org0.example.com添加。如果你指出COMPOSE_PROJECT_NAME env，当我回显它时，我得到的是空的响应。你能显式地将它设置为某个有意义的值并重试吗？你认为在对等基础中设置它。yaml spec？也适用于我。快速解决方案。谢谢是的，这也是我的案子的解决方案。我将我的.env
文件移动到了包含docker compose.yaml
文件的同一目录中。然后我不得不重新开始，创建频道
，并在该频道上设置链码。在那之后，其他一切都很顺利。
version: '2'

networks:
  yyy:   <----------------

services:
 ...
 ...
    - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=zzz
 ...
 ...

failed to invoke chaincode name:"lscc" , error: API error (404): network zzz not found

 CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=xxx_yyy