在将Hyperledger Fabric对等方部署到Kubernetes时获得“无法初始化加密”

时间:2019-02-13 06:39:20

标签: kubernetes hyperledger-fabric blockchain google-kubernetes-engine

我正在尝试在GCP上将一个对等的Hyperledger Fabric网络设置部署到Kubernetes,而在部署对等时我却遇到了错误-

  

“无法运行对等,因为无法初始化加密,缺少/ var / msp文件夹”

我尝试安装msp材质,但无法正常工作

这是对等配置-

  

apiVersion:apps / v1种类:部署元数据:名称:peer0规范:
  副本:1个选择器:       matchLabels:         应用:peer0模板:       元数据:         标签:           应用:peer0           层:后端           轨迹:稳定       规格:         hostAliases:         -ip:“ 10.128.0.3”           主机名:           -“ peer0.example.com”         -ip:“ 10.128.0.3”           主机名:           -“ couchdb0”         -ip:“ 10.128.0.4”           主机名:             -“ orderer0.orderer.com”         nodeSelector:           id:对等         容器:         -名称:peer0           图片:“超级分类帐/织物对等机:1.2.0”           端口:             -名称:peer0-port               containerPort:30002             -名称:peer0-chaincode               containerPort:30003             -名称:peer0-event               containerPort:30004           workingDir:/opt/gopath/src/github.com/hyperledger/fabric/peer           命令:[“ peer”]           args:[“ node”,“ start”]           环境:             -名称:CORE_VM_ENDPOINT               值:“ unix:///var/run/docker.sock”             -名称:CORE_PEER_ADDRESSAUTODETECT               值:“ true”             -名称:CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE               值:“桥”             -名称:CORE_PEER_ID               值:“ peer0.example.com”             -名称:CORE_PEER_ADDRESS               值:“ peer0.example.com:30002”             -名称:CORE_PEER_GOSSIP_EXTERNALENDPOINT               值:“ peer0.example.com:30002”             -名称:CORE_PEER_CHAINCODELISTENADDRESS               值:“ 0.0.0.0:30003”             -名称:CORE_PEER_GOSSIP_BOOTSTRAP               值:“ 0.0.0.0:30002”             -名称:CORE_PEER_LISTENADDRESS               值:“ 0.0.0.0:30002”             -名称:CORE_PEER_EVENTS_ADDRESS               值:“ 0.0.0.0:30004”             -名称:CORE_PEER_LOCALMSPID               值:“ exampleMSP”             -名称:CORE_LOGGING_GOSSIP               值:“ INFO”             -名称:CORE_LOGGING_PEER_GOSSIP               值:“ INFO”             -名称:CORE_LOGGING_MSP               值:“ INFO”             -名称:CORE_LOGGING_POLICIES               值:“ DEBUG”             -名称:CORE_LOGGING_CAUTHDSL               值:“ DEBUG”             -名称:CORE_PEER_TLS_ENABLED               值:“ false”             -名称:CORE_PEER_GOSSIP_USELEADERELECTION               值:“ true”             -名称:CORE_PEER_GOSSIP_ORGLEADER               值:“ false”             -名称:CORE_PEER_PROFILE_ENABLED               值:“ true”             -名称:CORE_LEDGER_STATE_STATEDATABASE               值:“ CouchDB”             -名称:CORE_PEER_GOSSIP_ORGLEADER               值:“ false”             -名称:CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS               值:“ couchdb0:30005”             -名称:ORDERER_URL               值:“ orderer0.orderer.com:30001”             -名称:CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME               值:“”             -名称:CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD               值:“”             -名称:CORE_VM_DOCKER_ATTACHSTDOUT               值:“ true”             -名称:CORE_PEER_FILESYSTEMPATH               值:“ / var / production”             -名称:CORE_PEER_MSPCONFIGPATH               #value:“ / var / msp”               值:“ / var / msp”           volumeMounts:             -名称:peer0-volume               mountPath:/ var             -名称:主持人               mountPath:/ var / run

  volumes:
    - name: peer0-volume
      #persistentVolumeClaim:
       # claimName: peer0-pvc
    - name: host
      hostPath:
        path: /var/run

2 个答案:

答案 0 :(得分:0)

引用James的评论

  

“我解决了这个问题,这是由于文件没有在容器内挂载而引起的,为此我添加了单独的挂载点,并且效果很好。”

答案 1 :(得分:0)

从npm尝试kubechain可能会有所帮助。