Hyperledger Fabric Java Chaincode 可以在没有 docker 的情况下安装和运行吗？
Can Hyperledger Fabric Java Chaincode installs and runs without docker?
我正在尝试在 Oracle Linux 8.4
上设置没有 docker 的 Hyperledger Fabric
我正在使用 github 版本的 fabric 2.2.3。
https://github.com/hyperledger/fabric/releases/download/v2.2.3/hyperledger-fabric-linux-amd64-2.2.3.tar.gz
我也在尝试通过不使用 fabric-ca 来了解它是如何工作的。
到目前为止，我设法完全使用 OpenSSL 和那些 MSP 目录创建了自己的证书层次结构和链...
通过证书链，我还设法
- 使用 cryptotxgen 生成创世块
- star订购者已准备就绪
- 使用 cryptotxgen 创建一个新通道（我将其命名为 orderer-channel）
- started peer 加入新频道
但是，我一直在链代码上遇到问题。
我正在尝试安装 Java 链码，同时使用
peer lifecycle chaincode package, peer lifecycle chaincode install VS peer chaincode package, peer chaincode install ... 运气不好
它不断提示我 docker 错误消息（请参阅下面的日志）
如何在没有 docker 的情况下部署我的链代码？
我已经尝试使用 --peer-chaincodedev star 对等方进行 star...但也没有任何运气
从下面的日志中，如果使用链代码安装（没有生命周期），它报告安装成功，但在 docker 上失败。
因此，作为我的主题，是否可以在没有 docker 的情况下安装和 运行 链代码？
到目前为止，我在没有 docker 的情况下自行设置和配置，现在在最后一步似乎迫使我使用 docker >__<
使用生命周期链代码安装的安装链代码日志：
[user@hyperledgerfabric ~]# /appl/hyperledger-fabric/bin/peer lifecycle chaincode install /appl/chaincode/TestHLF-1.0.0.tar.gz --peerAddresses localhost:7051 -o localhost:7050
Error: chaincode install failed with status: 500 - failed to invoke backing implementation of 'InstallChaincode': could not build chaincode: docker build failed: docker image inspection failed: Get "http://unix.sock/images/testhlf-1.0.0-da9445c8699c299812759f4072a8069875a786f4382b00591b87c1feab4c9599-721fab386a2ac9009bd0e40582127b7895df36b6a1d74dfb108713d1b4751cd5/json": dial unix /var/run/docker.sock: connect: no such file or directory
使用链码安装（无生命周期）安装链码的日志：
[user@hyperledgerfabric ~]# /appl/hyperledger-fabric/bin/peer chaincode install -l java -p /appl/chaincode/TestHLF -n TestHLF -v 1.0.0 --peerAddresses localhost:7051 -o localhost:7050
2021-09-01 17:45:02.804 +08 [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
2021-09-01 17:45:02.804 +08 [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
Error: install failed with status: 500 - chaincode installed to peer but could not build chaincode: docker build failed: docker image inspection failed: Get "http://unix.sock/images/testhlf-1.0.0-0e6bfac3b09ead9a0bd3e887e68ea728650f7c9e87b335ec6f539517b834ba08/json": dial unix /var/run/docker.sock: connect: no such file or directory
[user@hyperledgerfabric ~]# /appl/hyperledger-fabric/bin/peer chaincode list -C orderer-channel --peerAddresses localhost:7051 --installed
Get installed chaincodes on peer:
Name: TestHLF, Version: 1.0.0, Path: /appl/chaincode/TestHLF, Id: c57c51536a53f01ee95324a2de8a564d9485ecf86c313c7baa9348cd8ec70d96
外部构建器和启动器的更新：
尝试使用 External Builder，但它似乎仍在我的同行中寻找我的 docker。
metadata.json中的变量path，是干什么用的？
[user@hyperledgerfabric TestHLF]# /appl/hyperledger-fabric/bin/peer lifecycle chaincode install --peerAddresses localhost:7051 /appl/chaincode-builder/TestHLF/TestHLF.tar.gz
Error: chaincode install failed with status: 500 - failed to invoke backing implementation of 'InstallChaincode': could not build chaincode: docker build failed: docker image inspection failed: Get "http://unix.sock/images/testhlf-5cb99feb2a9be27749bfc0f05d93cddaf8b23a9023c3bbc217aebcb703082141-941a0fbcc36e8019c4cd118263ce7a6ba266432dc0a4d7e6b5a07554ba3d1923/json": dial unix /var/run/docker.sock: connect: no such file or directory
我更新了我的 core.yaml 在我的同伴中指向外部构建器。
[user@hyperledgerfabric TestHLF]# grep externalBuilder -A3 /appl/blockchain/_config/core.yaml
# externalBuilders: []
externalBuilders:
- path: /appl/chaincode-builder/TestHLF
name: testhlf-builder
这里是tar的内容，还有重要文件的内容。
[user@hyperledgerfabric TestHLF]# tar -tvf /appl/chaincode-builder/TestHLF/TestHLF.tar.gz
-rw-r--r-- fabric/fabric 61 2021-09-02 10:29 metadata.json
-rw-r--r-- fabric/fabric 229 2021-09-02 10:29 code.tar.gz
[user@hyperledgerfabric TestHLF]# tar -tvf /appl/chaincode-builder/TestHLF/code.tar.gz
-rw-r--r-- fabric/fabric 150 2021-09-02 10:29 connection.json
[user@hyperledgerfabric TestHLF]# cat /appl/chaincode-builder/TestHLF/metadata.json
{
"path": "",
"type": "external",
"label": "TestHLF"
}
[user@hyperledgerfabric TestHLF]# cat /appl/chaincode-builder/TestHLF/connection.json
{
"address": "localhost:9999",
"dial_timeout": "10s",
"tls_required": "false",
"client_auth_required": "false"
}
[user@hyperledgerfabric TestHLF]# ls -l bin
total 12
-rwxr-xr-x. 1 fabric fabric 307 Sep 2 10:42 build
-rwxr-xr-x. 1 fabric fabric 243 Sep 2 10:29 detect
-rwxr-xr-x. 1 fabric fabric 219 Sep 2 10:42 release
外部构建器和启动器的更新 (2)：
这里有更多关于检测、构建和发布可执行文件的详细信息。
从之前的更新开始，可执行文件的权限为 755。
还有可执行文件来测试它是否有效，我没有做检查，只是试图输出值。
在我看来它甚至没有调用可执行文件。
[user@hyperledgerfabric bin]# cat build
#!/bin/bash
CHAINCODE_SOURCE_DIR=
CHAINCODE_METADATA_DIR=
BUILD_OUTPUT_DIR=
echo "CHAINCODE_SOURCE_DIR = $CHAINCODE_SOURCE_DIR"
echo "CHAINCODE_METADATA_DIR = $CHAINCODE_METADATA_DIR"
echo "BUILD_OUTPUT_DIR = $BUILD_OUTPUT_DIR"
touch /appl/chaincode-builder/TestHLF/touch02.txt
exit 0
[user@hyperledgerfabric bin]# cat detect
#!/bin/bash
CHAINCODE_SOURCE_DIR=
CHAINCODE_METADATA_DIR=
echo "CHAINCODE_SOURCE_DIR = $CHAINCODE_SOURCE_DIR"
echo "CHAINCODE_METADATA_DIR = $CHAINCODE_METADATA_DIR"
touch /appl/chaincode-builder/TestHLF/touch01.txt
exit 0
[user@hyperledgerfabric bin]# cat release
#!/bin/bash
BUILD_OUTPUT_DIR=
RELEASE_OUTPUT_DIR=
echo "BUILD_OUTPUT_DIR = $BUILD_OUTPUT_DIR"
echo "RELEASE_OUTPUT_DIR = $RELEASE_OUTPUT_DIR"
touch /appl/chaincode-builder/TestHLF/touch03.txt
exit 0
外部构建器和启动器的更新 (3)：
我使用FABRIC_LOGGING_SPEC=debug
打开调试模式
这是调试日志，我没有看到任何关于调用我的可执行文件的信息。
调试对等登录：
Sep 02 17:04:35 hyperledgerfabric peer[1588]: 2021-09-02 17:04:35.254 +08 [lifecycle] InstallChaincode -> DEBU 49d received invocation of InstallChaincode for install package 1f8b08001c9130610003cb4d2d494c492c49d4cb2acecf63a00d300002331313106d68...
Sep 02 17:04:35 hyperledgerfabric peer[1588]: 2021-09-02 17:04:35.254 +08 [ccprovider] MetadataAsTarEntries -> DEBU 49e Created metadata tar
Sep 02 17:04:35 hyperledgerfabric peer[1588]: 2021-09-02 17:04:35.255 +08 [chaincode] handleMessage -> DEBU 49f [a0343dde] Fabric side handling ChaincodeMessage of type: COMPLETED in state ready
Sep 02 17:04:35 hyperledgerfabric peer[1588]: 2021-09-02 17:04:35.255 +08 [chaincode] Notify -> DEBU 4a0 [a0343dde] notifying Txid:a0343ddee86f669b143923992bd36e6b735b39de681dfb8f230c10af3f469410, channelID:
Sep 02 17:04:35 hyperledgerfabric peer[1588]: 2021-09-02 17:04:35.255 +08 [chaincode] Execute -> DEBU 4a1 Exit
Sep 02 17:04:35 hyperledgerfabric peer[1588]: 2021-09-02 17:04:35.255 +08 [endorser] callChaincode -> INFO 4a2 finished chaincode: _lifecycle duration: 1ms channel= txID=a0343dde
Sep 02 17:04:35 hyperledgerfabric peer[1588]: 2021-09-02 17:04:35.255 +08 [comm.grpc.server] 1 -> INFO 4a3 unary call completed grpc.service=protos.Endorser grpc.method=ProcessProposal grpc.peer_address=[::1]:35628 grpc.code=OK grpc.call_duration=1.805332ms
Sep 02 17:04:35 hyperledgerfabric peer[1588]: 2021-09-02 17:04:35.257 +08 [grpc] infof -> DEBU 4a4 transport: loopyWriter.run returning. connection error: desc = "transport is closing"
Sep 02 17:04:35 hyperledgerfabric peer[1588]: 2021-09-02 17:04:35.257 +08 [grpc] infof -> DEBU 4a5 transport: loopyWriter.run returning. connection error: desc = "transport is closing"
调用生命周期链代码安装时的调试日志：
2021-09-02 17:04:35.245 +08 [msp] setupSigningIdentity -> DEBU 01a Signing identity expires at 2041-08-24 07:42:50 +0000 UTC
2021-09-02 17:04:35.246 +08 [msp] GetDefaultSigningIdentity -> DEBU 01b Obtaining default signing identity
2021-09-02 17:04:35.248 +08 [grpc] Infof -> DEBU 01c parsed scheme: ""
2021-09-02 17:04:35.248 +08 [grpc] Infof -> DEBU 01d scheme "" not registered, fallback to default scheme
2021-09-02 17:04:35.248 +08 [grpc] Infof -> DEBU 01e ccResolverWrapper: sending update to cc: {[{localhost:7051 <nil> 0 <nil>}] <nil> <nil>}
2021-09-02 17:04:35.249 +08 [grpc] Infof -> DEBU 01f ClientConn switching balancer to "pick_first"
2021-09-02 17:04:35.249 +08 [grpc] Infof -> DEBU 020 Channel switches to new LB policy "pick_first"
2021-09-02 17:04:35.249 +08 [grpc] Infof -> DEBU 021 Subchannel Connectivity change to CONNECTING
2021-09-02 17:04:35.249 +08 [grpc] Infof -> DEBU 022 Subchannel picks a new address "localhost:7051" to connect
2021-09-02 17:04:35.249 +08 [grpc] UpdateSubConnState -> DEBU 023 pickfirstBalancer: HandleSubConnStateChange: 0xc00040f7f0, {CONNECTING <nil>}
2021-09-02 17:04:35.249 +08 [grpc] Infof -> DEBU 024 Channel Connectivity change to CONNECTING
2021-09-02 17:04:35.251 +08 [grpc] Infof -> DEBU 025 Subchannel Connectivity change to READY
2021-09-02 17:04:35.251 +08 [grpc] UpdateSubConnState -> DEBU 026 pickfirstBalancer: HandleSubConnStateChange: 0xc00040f7f0, {READY <nil>}
2021-09-02 17:04:35.251 +08 [grpc] Infof -> DEBU 027 Channel Connectivity change to READY
2021-09-02 17:04:35.251 +08 [grpc] Infof -> DEBU 028 parsed scheme: ""
2021-09-02 17:04:35.251 +08 [grpc] Infof -> DEBU 029 scheme "" not registered, fallback to default scheme
2021-09-02 17:04:35.251 +08 [grpc] Infof -> DEBU 02a ccResolverWrapper: sending update to cc: {[{localhost:7051 <nil> 0 <nil>}] <nil> <nil>}
2021-09-02 17:04:35.251 +08 [grpc] Infof -> DEBU 02b ClientConn switching balancer to "pick_first"
2021-09-02 17:04:35.251 +08 [grpc] Infof -> DEBU 02c Channel switches to new LB policy "pick_first"
2021-09-02 17:04:35.251 +08 [grpc] Infof -> DEBU 02d Subchannel Connectivity change to CONNECTING
2021-09-02 17:04:35.251 +08 [grpc] Infof -> DEBU 02e Subchannel picks a new address "localhost:7051" to connect
2021-09-02 17:04:35.251 +08 [grpc] UpdateSubConnState -> DEBU 02f pickfirstBalancer: HandleSubConnStateChange: 0xc000283ec0, {CONNECTING <nil>}
2021-09-02 17:04:35.252 +08 [grpc] Infof -> DEBU 030 Channel Connectivity change to CONNECTING
2021-09-02 17:04:35.252 +08 [grpc] Infof -> DEBU 031 Subchannel Connectivity change to READY
2021-09-02 17:04:35.252 +08 [grpc] UpdateSubConnState -> DEBU 032 pickfirstBalancer: HandleSubConnStateChange: 0xc000283ec0, {READY <nil>}
2021-09-02 17:04:35.252 +08 [grpc] Infof -> DEBU 033 Channel Connectivity change to READY
2021-09-02 17:04:35.253 +08 [msp.identity] Sign -> DEBU 034 Sign: plaintext: 0ACB080A6108031A0B08A3A7C2890610...05A36014D00F00005318644000280000
2021-09-02 17:04:35.253 +08 [msp.identity] Sign -> DEBU 035 Sign: digest: 6C40B4067E4B357821801A1314B2D276BCD3E5B60AF86CDD11AC93776F0A0EBE
Error: chaincode install failed with status: 500 - failed to invoke backing implementation of 'InstallChaincode': could not build chaincode: docker build failed: docker image inspection failed: Get "http://unix.sock/images/testhlf-d092ae78b2f02de3ae597e09cfe84543dc97a65588b2f78e2dd0260811963252-84293d54f47de427b969eef63391a9deca67ecff063052fda66e267832490491/json": dial unix /var/run/docker.sock: connect: no such file or directory
您的 docker 问题似乎是对等点找不到 Docker daemon socket 它期望启动链码容器的地方。
节点内的 docker 守护程序位置是通过环境变量配置的：
- CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
它通常从对等容器 运行 所在的文件系统映射，通过一个卷：
- /var/run/:/host/var/run/
因此，如果您的对等方 运行 在具有 运行 docker 守护程序 Unix 套接字的机器上，这应该很容易通过找到套接字（并检查其权限）来修复) 并配置您的同行。
作为替代方案，您还可以在 CORE_VM_ENDPOINT 中配置 Docker TCP endpoint，而不是 Unix 套接字。
如果这一切在您的环境中是不可能的（如果您在某种限制性环境中工作），您始终可以在您的同行上启用 External Builders and Launchers 并适当地部署您的链代码。这将是对您的问题标题的具体答复：YES，通过外部构建器和启动器。但这比适当配置对 docker 守护程序的访问要复杂得多。
您对 CA 的所有考虑都不会解决您的问题。但是，在您的生产环境中，您应该使用某种 CA...
我正在尝试在 Oracle Linux 8.4
上设置没有 docker 的 Hyperledger Fabric我正在使用 github 版本的 fabric 2.2.3。
https://github.com/hyperledger/fabric/releases/download/v2.2.3/hyperledger-fabric-linux-amd64-2.2.3.tar.gz
我也在尝试通过不使用 fabric-ca 来了解它是如何工作的。
到目前为止，我设法完全使用 OpenSSL 和那些 MSP 目录创建了自己的证书层次结构和链... 通过证书链，我还设法
- 使用 cryptotxgen 生成创世块
- star订购者已准备就绪
- 使用 cryptotxgen 创建一个新通道（我将其命名为 orderer-channel）
- started peer 加入新频道
但是，我一直在链代码上遇到问题。
我正在尝试安装 Java 链码，同时使用
peer lifecycle chaincode package, peer lifecycle chaincode install VS peer chaincode package, peer chaincode install ... 运气不好
它不断提示我 docker 错误消息（请参阅下面的日志）
如何在没有 docker 的情况下部署我的链代码？ 我已经尝试使用 --peer-chaincodedev star 对等方进行 star...但也没有任何运气
从下面的日志中，如果使用链代码安装（没有生命周期），它报告安装成功，但在 docker 上失败。
因此，作为我的主题，是否可以在没有 docker 的情况下安装和 运行 链代码？
到目前为止，我在没有 docker 的情况下自行设置和配置，现在在最后一步似乎迫使我使用 docker >__<
使用生命周期链代码安装的安装链代码日志：
[user@hyperledgerfabric ~]# /appl/hyperledger-fabric/bin/peer lifecycle chaincode install /appl/chaincode/TestHLF-1.0.0.tar.gz --peerAddresses localhost:7051 -o localhost:7050
Error: chaincode install failed with status: 500 - failed to invoke backing implementation of 'InstallChaincode': could not build chaincode: docker build failed: docker image inspection failed: Get "http://unix.sock/images/testhlf-1.0.0-da9445c8699c299812759f4072a8069875a786f4382b00591b87c1feab4c9599-721fab386a2ac9009bd0e40582127b7895df36b6a1d74dfb108713d1b4751cd5/json": dial unix /var/run/docker.sock: connect: no such file or directory
使用链码安装（无生命周期）安装链码的日志：
[user@hyperledgerfabric ~]# /appl/hyperledger-fabric/bin/peer chaincode install -l java -p /appl/chaincode/TestHLF -n TestHLF -v 1.0.0 --peerAddresses localhost:7051 -o localhost:7050
2021-09-01 17:45:02.804 +08 [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
2021-09-01 17:45:02.804 +08 [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
Error: install failed with status: 500 - chaincode installed to peer but could not build chaincode: docker build failed: docker image inspection failed: Get "http://unix.sock/images/testhlf-1.0.0-0e6bfac3b09ead9a0bd3e887e68ea728650f7c9e87b335ec6f539517b834ba08/json": dial unix /var/run/docker.sock: connect: no such file or directory
[user@hyperledgerfabric ~]# /appl/hyperledger-fabric/bin/peer chaincode list -C orderer-channel --peerAddresses localhost:7051 --installed
Get installed chaincodes on peer:
Name: TestHLF, Version: 1.0.0, Path: /appl/chaincode/TestHLF, Id: c57c51536a53f01ee95324a2de8a564d9485ecf86c313c7baa9348cd8ec70d96
外部构建器和启动器的更新：
尝试使用 External Builder，但它似乎仍在我的同行中寻找我的 docker。
metadata.json中的变量path，是干什么用的？
[user@hyperledgerfabric TestHLF]# /appl/hyperledger-fabric/bin/peer lifecycle chaincode install --peerAddresses localhost:7051 /appl/chaincode-builder/TestHLF/TestHLF.tar.gz
Error: chaincode install failed with status: 500 - failed to invoke backing implementation of 'InstallChaincode': could not build chaincode: docker build failed: docker image inspection failed: Get "http://unix.sock/images/testhlf-5cb99feb2a9be27749bfc0f05d93cddaf8b23a9023c3bbc217aebcb703082141-941a0fbcc36e8019c4cd118263ce7a6ba266432dc0a4d7e6b5a07554ba3d1923/json": dial unix /var/run/docker.sock: connect: no such file or directory
我更新了我的 core.yaml 在我的同伴中指向外部构建器。
[user@hyperledgerfabric TestHLF]# grep externalBuilder -A3 /appl/blockchain/_config/core.yaml
# externalBuilders: []
externalBuilders:
- path: /appl/chaincode-builder/TestHLF
name: testhlf-builder
这里是tar的内容，还有重要文件的内容。
[user@hyperledgerfabric TestHLF]# tar -tvf /appl/chaincode-builder/TestHLF/TestHLF.tar.gz
-rw-r--r-- fabric/fabric 61 2021-09-02 10:29 metadata.json
-rw-r--r-- fabric/fabric 229 2021-09-02 10:29 code.tar.gz
[user@hyperledgerfabric TestHLF]# tar -tvf /appl/chaincode-builder/TestHLF/code.tar.gz
-rw-r--r-- fabric/fabric 150 2021-09-02 10:29 connection.json
[user@hyperledgerfabric TestHLF]# cat /appl/chaincode-builder/TestHLF/metadata.json
{
"path": "",
"type": "external",
"label": "TestHLF"
}
[user@hyperledgerfabric TestHLF]# cat /appl/chaincode-builder/TestHLF/connection.json
{
"address": "localhost:9999",
"dial_timeout": "10s",
"tls_required": "false",
"client_auth_required": "false"
}
[user@hyperledgerfabric TestHLF]# ls -l bin
total 12
-rwxr-xr-x. 1 fabric fabric 307 Sep 2 10:42 build
-rwxr-xr-x. 1 fabric fabric 243 Sep 2 10:29 detect
-rwxr-xr-x. 1 fabric fabric 219 Sep 2 10:42 release
外部构建器和启动器的更新 (2)：
这里有更多关于检测、构建和发布可执行文件的详细信息。
从之前的更新开始，可执行文件的权限为 755。
还有可执行文件来测试它是否有效，我没有做检查，只是试图输出值。
在我看来它甚至没有调用可执行文件。
[user@hyperledgerfabric bin]# cat build
#!/bin/bash
CHAINCODE_SOURCE_DIR=
CHAINCODE_METADATA_DIR=
BUILD_OUTPUT_DIR=
echo "CHAINCODE_SOURCE_DIR = $CHAINCODE_SOURCE_DIR"
echo "CHAINCODE_METADATA_DIR = $CHAINCODE_METADATA_DIR"
echo "BUILD_OUTPUT_DIR = $BUILD_OUTPUT_DIR"
touch /appl/chaincode-builder/TestHLF/touch02.txt
exit 0
[user@hyperledgerfabric bin]# cat detect
#!/bin/bash
CHAINCODE_SOURCE_DIR=
CHAINCODE_METADATA_DIR=
echo "CHAINCODE_SOURCE_DIR = $CHAINCODE_SOURCE_DIR"
echo "CHAINCODE_METADATA_DIR = $CHAINCODE_METADATA_DIR"
touch /appl/chaincode-builder/TestHLF/touch01.txt
exit 0
[user@hyperledgerfabric bin]# cat release
#!/bin/bash
BUILD_OUTPUT_DIR=
RELEASE_OUTPUT_DIR=
echo "BUILD_OUTPUT_DIR = $BUILD_OUTPUT_DIR"
echo "RELEASE_OUTPUT_DIR = $RELEASE_OUTPUT_DIR"
touch /appl/chaincode-builder/TestHLF/touch03.txt
exit 0
外部构建器和启动器的更新 (3)：
我使用FABRIC_LOGGING_SPEC=debug
打开调试模式
这是调试日志，我没有看到任何关于调用我的可执行文件的信息。
调试对等登录：
Sep 02 17:04:35 hyperledgerfabric peer[1588]: 2021-09-02 17:04:35.254 +08 [lifecycle] InstallChaincode -> DEBU 49d received invocation of InstallChaincode for install package 1f8b08001c9130610003cb4d2d494c492c49d4cb2acecf63a00d300002331313106d68...
Sep 02 17:04:35 hyperledgerfabric peer[1588]: 2021-09-02 17:04:35.254 +08 [ccprovider] MetadataAsTarEntries -> DEBU 49e Created metadata tar
Sep 02 17:04:35 hyperledgerfabric peer[1588]: 2021-09-02 17:04:35.255 +08 [chaincode] handleMessage -> DEBU 49f [a0343dde] Fabric side handling ChaincodeMessage of type: COMPLETED in state ready
Sep 02 17:04:35 hyperledgerfabric peer[1588]: 2021-09-02 17:04:35.255 +08 [chaincode] Notify -> DEBU 4a0 [a0343dde] notifying Txid:a0343ddee86f669b143923992bd36e6b735b39de681dfb8f230c10af3f469410, channelID:
Sep 02 17:04:35 hyperledgerfabric peer[1588]: 2021-09-02 17:04:35.255 +08 [chaincode] Execute -> DEBU 4a1 Exit
Sep 02 17:04:35 hyperledgerfabric peer[1588]: 2021-09-02 17:04:35.255 +08 [endorser] callChaincode -> INFO 4a2 finished chaincode: _lifecycle duration: 1ms channel= txID=a0343dde
Sep 02 17:04:35 hyperledgerfabric peer[1588]: 2021-09-02 17:04:35.255 +08 [comm.grpc.server] 1 -> INFO 4a3 unary call completed grpc.service=protos.Endorser grpc.method=ProcessProposal grpc.peer_address=[::1]:35628 grpc.code=OK grpc.call_duration=1.805332ms
Sep 02 17:04:35 hyperledgerfabric peer[1588]: 2021-09-02 17:04:35.257 +08 [grpc] infof -> DEBU 4a4 transport: loopyWriter.run returning. connection error: desc = "transport is closing"
Sep 02 17:04:35 hyperledgerfabric peer[1588]: 2021-09-02 17:04:35.257 +08 [grpc] infof -> DEBU 4a5 transport: loopyWriter.run returning. connection error: desc = "transport is closing"
调用生命周期链代码安装时的调试日志：
2021-09-02 17:04:35.245 +08 [msp] setupSigningIdentity -> DEBU 01a Signing identity expires at 2041-08-24 07:42:50 +0000 UTC
2021-09-02 17:04:35.246 +08 [msp] GetDefaultSigningIdentity -> DEBU 01b Obtaining default signing identity
2021-09-02 17:04:35.248 +08 [grpc] Infof -> DEBU 01c parsed scheme: ""
2021-09-02 17:04:35.248 +08 [grpc] Infof -> DEBU 01d scheme "" not registered, fallback to default scheme
2021-09-02 17:04:35.248 +08 [grpc] Infof -> DEBU 01e ccResolverWrapper: sending update to cc: {[{localhost:7051 <nil> 0 <nil>}] <nil> <nil>}
2021-09-02 17:04:35.249 +08 [grpc] Infof -> DEBU 01f ClientConn switching balancer to "pick_first"
2021-09-02 17:04:35.249 +08 [grpc] Infof -> DEBU 020 Channel switches to new LB policy "pick_first"
2021-09-02 17:04:35.249 +08 [grpc] Infof -> DEBU 021 Subchannel Connectivity change to CONNECTING
2021-09-02 17:04:35.249 +08 [grpc] Infof -> DEBU 022 Subchannel picks a new address "localhost:7051" to connect
2021-09-02 17:04:35.249 +08 [grpc] UpdateSubConnState -> DEBU 023 pickfirstBalancer: HandleSubConnStateChange: 0xc00040f7f0, {CONNECTING <nil>}
2021-09-02 17:04:35.249 +08 [grpc] Infof -> DEBU 024 Channel Connectivity change to CONNECTING
2021-09-02 17:04:35.251 +08 [grpc] Infof -> DEBU 025 Subchannel Connectivity change to READY
2021-09-02 17:04:35.251 +08 [grpc] UpdateSubConnState -> DEBU 026 pickfirstBalancer: HandleSubConnStateChange: 0xc00040f7f0, {READY <nil>}
2021-09-02 17:04:35.251 +08 [grpc] Infof -> DEBU 027 Channel Connectivity change to READY
2021-09-02 17:04:35.251 +08 [grpc] Infof -> DEBU 028 parsed scheme: ""
2021-09-02 17:04:35.251 +08 [grpc] Infof -> DEBU 029 scheme "" not registered, fallback to default scheme
2021-09-02 17:04:35.251 +08 [grpc] Infof -> DEBU 02a ccResolverWrapper: sending update to cc: {[{localhost:7051 <nil> 0 <nil>}] <nil> <nil>}
2021-09-02 17:04:35.251 +08 [grpc] Infof -> DEBU 02b ClientConn switching balancer to "pick_first"
2021-09-02 17:04:35.251 +08 [grpc] Infof -> DEBU 02c Channel switches to new LB policy "pick_first"
2021-09-02 17:04:35.251 +08 [grpc] Infof -> DEBU 02d Subchannel Connectivity change to CONNECTING
2021-09-02 17:04:35.251 +08 [grpc] Infof -> DEBU 02e Subchannel picks a new address "localhost:7051" to connect
2021-09-02 17:04:35.251 +08 [grpc] UpdateSubConnState -> DEBU 02f pickfirstBalancer: HandleSubConnStateChange: 0xc000283ec0, {CONNECTING <nil>}
2021-09-02 17:04:35.252 +08 [grpc] Infof -> DEBU 030 Channel Connectivity change to CONNECTING
2021-09-02 17:04:35.252 +08 [grpc] Infof -> DEBU 031 Subchannel Connectivity change to READY
2021-09-02 17:04:35.252 +08 [grpc] UpdateSubConnState -> DEBU 032 pickfirstBalancer: HandleSubConnStateChange: 0xc000283ec0, {READY <nil>}
2021-09-02 17:04:35.252 +08 [grpc] Infof -> DEBU 033 Channel Connectivity change to READY
2021-09-02 17:04:35.253 +08 [msp.identity] Sign -> DEBU 034 Sign: plaintext: 0ACB080A6108031A0B08A3A7C2890610...05A36014D00F00005318644000280000
2021-09-02 17:04:35.253 +08 [msp.identity] Sign -> DEBU 035 Sign: digest: 6C40B4067E4B357821801A1314B2D276BCD3E5B60AF86CDD11AC93776F0A0EBE
Error: chaincode install failed with status: 500 - failed to invoke backing implementation of 'InstallChaincode': could not build chaincode: docker build failed: docker image inspection failed: Get "http://unix.sock/images/testhlf-d092ae78b2f02de3ae597e09cfe84543dc97a65588b2f78e2dd0260811963252-84293d54f47de427b969eef63391a9deca67ecff063052fda66e267832490491/json": dial unix /var/run/docker.sock: connect: no such file or directory
您的 docker 问题似乎是对等点找不到 Docker daemon socket 它期望启动链码容器的地方。
节点内的 docker 守护程序位置是通过环境变量配置的：
- CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
它通常从对等容器 运行 所在的文件系统映射，通过一个卷：
- /var/run/:/host/var/run/
因此，如果您的对等方 运行 在具有 运行 docker 守护程序 Unix 套接字的机器上，这应该很容易通过找到套接字（并检查其权限）来修复) 并配置您的同行。
作为替代方案，您还可以在 CORE_VM_ENDPOINT 中配置 Docker TCP endpoint，而不是 Unix 套接字。
如果这一切在您的环境中是不可能的（如果您在某种限制性环境中工作），您始终可以在您的同行上启用 External Builders and Launchers 并适当地部署您的链代码。这将是对您的问题标题的具体答复：YES，通过外部构建器和启动器。但这比适当配置对 docker 守护程序的访问要复杂得多。
您对 CA 的所有考虑都不会解决您的问题。但是，在您的生产环境中，您应该使用某种 CA...