352-fabric配置和启动fabric网络

最新推荐文章于 2022-03-28 11:33:48 发布
最新推荐文章于 2022-03-28 11:33:48 发布
阅读量975 收藏 2
点赞数 2
分类专栏： fabric
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_33781658/article/details/89302796
版权 







fabric配置和启动fabric网络








先看下目录
abc@abc:~/workspace/fabric$ ls
abc.yaml  channel.tx     crypto-config            genesis.block  template.yaml
base      configtx.yaml  docker-compose-cli.yaml  sample


然后我们找到docker-compose-cli.yaml
和base下面的
docker-compose-base.yaml  peer-base.yaml

1.docker-compose-cli
2.docker-compose-base
3.peer-base






我们先来修改一下
docker-compose-cli




# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

version: '2'

volumes:
  orderer.abc.com:
  peer0.org1.abc.com:
  peer1.org1.abc.com:
  peer0.org2.abc.com:
  peer1.org2.abc.com:

networks:
  byfn:

services:

  orderer.abc.com:
    extends:
      file:   base/docker-compose-base.yaml
      service: orderer.abc.com
    container_name: orderer.abc.com
    networks:
      - byfn

  peer0.org1.abc.com:
    container_name: peer0.org1.abc.com
    extends:
      file:  base/docker-compose-base.yaml
      service: peer0.org1.abc.com
    networks:
      - byfn

  peer1.org1.abc.com:
    container_name: peer1.org1.abc.com
    extends:
      file:  base/docker-compose-base.yaml
      service: peer1.org1.abc.com
    networks:
      - byfn

  peer0.org2.abc.com:
    container_name: peer0.org2.abc.com
    extends:
      file:  base/docker-compose-base.yaml
      service: peer0.org2.abc.com
    networks:
      - byfn

  peer1.org2.abc.com:
    container_name: peer1.org2.abc.com
    extends:
      file:  base/docker-compose-base.yaml
      service: peer1.org2.abc.com
    networks:
      - byfn

  cli:
    container_name: cli
    image: hyperledger/fabric-tools:$IMAGE_TAG
    tty: true
    stdin_open: true
    environment:
      - GOPATH=/opt/gopath
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      #- FABRIC_LOGGING_SPEC=DEBUG
      - FABRIC_LOGGING_SPEC=INFO
      - CORE_PEER_ID=cli
      - CORE_PEER_ADDRESS=peer0.org1.abc.com:7051
      - CORE_PEER_LOCALMSPID=Org1MSP
      - CORE_PEER_TLS_ENABLED=true
      - CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.abc.com/peers/peer0.org1.abc.com/tls/server.crt
      - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.abc.com/peers/peer0.org1.abc.com/tls/server.key
      - CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.abc.com/peers/peer0.org1.abc.com/tls/ca.crt
      - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.abc.com/users/Admin@org1.abc.com/msp
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    command: /bin/bash
    volumes:
        - /var/run/:/host/var/run/
        - ./../chaincode/:/opt/gopath/src/github.com/chaincode
        - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
        - ./scripts:/opt/gopath/src/github.com/hyperledger/fabric/peer/scripts/
        - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts
    depends_on:
      - orderer.abc.com
      - peer0.org1.abc.com
      - peer1.org1.abc.com
      - peer0.org2.abc.com
      - peer1.org2.abc.com
    networks:
      - byfn






我们创建一个chaincode文件夹
mkdir chaincode
如果不创建的话,会自动创建
但是用户组是root
如果我们自己创建的话,用户组是go


我们再创建一个channel-artifacts文件夹
把channel.tx和genesis.block放到里面去

然后我们再看一下目录
abc@abc:~/workspace/fabric$ ls
abc.yaml  chaincode          configtx.yaml  docker-compose-cli.yaml
base      channel-artifacts  crypto-config  sample
 










然后我们来修改
docker-compose-base


# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

version: '2'

services:

  orderer.abc.com:
    container_name: orderer.abc.com
    extends:
      file: peer-base.yaml
      service: orderer-base
    volumes:
        - ../channel-artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block
        - ../crypto-config/ordererOrganizations/abc.com/orderers/orderer.abc.com/msp:/var/hyperledger/orderer/msp
        - ../crypto-config/ordererOrganizations/abc.com/orderers/orderer.abc.com/tls/:/var/hyperledger/orderer/tls
        - orderer.abc.com:/var/hyperledger/production/orderer
    ports:
      - 7050:7050

  peer0.org1.abc.com:
    container_name: peer0.org1.abc.com
    extends:
      file: peer-base.yaml
      service: peer-base
    environment:
      - CORE_PEER_ID=peer0.org1.abc.com
      - CORE_PEER_ADDRESS=peer0.org1.abc.com:7051
      - CORE_PEER_LISTENADDRESS=0.0.0.0:7051
      - CORE_PEER_CHAINCODEADDRESS=peer0.org1.abc.com:7052
      - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7052
      - CORE_PEER_GOSSIP_BOOTSTRAP=peer1.org1.abc.com:8051
      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org1.abc.com:7051
      - CORE_PEER_LOCALMSPID=Org1MSP
    volumes:
        - /var/run/:/host/var/run/
        - ../crypto-config/peerOrganizations/org1.abc.com/peers/peer0.org1.abc.com/msp:/etc/hyperledger/fabric/msp
        - ../crypto-config/peerOrganizations/org1.abc.com/peers/peer0.org1.abc.com/tls:/etc/hyperledger/fabric/tls
        - peer0.org1.abc.com:/var/hyperledger/production
    ports:
      - 7051:7051

  peer1.org1.abc.com:
    container_name: peer1.org1.abc.com
    extends:
      file: peer-base.yaml
      service: peer-base
    environment:
      - CORE_PEER_ID=peer1.org1.abc.com
      - CORE_PEER_ADDRESS=peer1.org1.abc.com:8051
      - CORE_PEER_LISTENADDRESS=0.0.0.0:8051
      - CORE_PEER_CHAINCODEADDRESS=peer1.org1.abc.com:8052
      - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:8052
      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer1.org1.abc.com:8051
      - CORE_PEER_GOSSIP_BOOTSTRAP=peer0.org1.abc.com:7051
      - CORE_PEER_LOCALMSPID=Org1MSP
    volumes:
        - /var/run/:/host/var/run/
        - ../crypto-config/peerOrganizations/org1.abc.com/peers/peer1.org1.abc.com/msp:/etc/hyperledger/fabric/msp
        - ../crypto-config/peerOrganizations/org1.abc.com/peers/peer1.org1.abc.com/tls:/etc/hyperledger/fabric/tls
        - peer1.org1.abc.com:/var/hyperledger/production

    ports:
      - 8051:8051

  peer0.org2.abc.com:
    container_name: peer0.org2.abc.com
    extends:
      file: peer-base.yaml
      service: peer-base
    environment:
      - CORE_PEER_ID=peer0.org2.abc.com
      - CORE_PEER_ADDRESS=peer0.org2.abc.com:9051
      - CORE_PEER_LISTENADDRESS=0.0.0.0:9051
      - CORE_PEER_CHAINCODEADDRESS=peer0.org2.abc.com:9052
      - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:9052
      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org2.abc.com:9051
      - CORE_PEER_GOSSIP_BOOTSTRAP=peer1.org2.abc.com:10051
      - CORE_PEER_LOCALMSPID=Org2MSP
    volumes:
        - /var/run/:/host/var/run/
        - ../crypto-config/peerOrganizations/org2.abc.com/peers/peer0.org2.abc.com/msp:/etc/hyperledger/fabric/msp
        - ../crypto-config/peerOrganizations/org2.abc.com/peers/peer0.org2.abc.com/tls:/etc/hyperledger/fabric/tls
        - peer0.org2.abc.com:/var/hyperledger/production
    ports:
      - 9051:9051

  peer1.org2.abc.com:
    container_name: peer1.org2.abc.com
    extends:
      file: peer-base.yaml
      service: peer-base
    environment:
      - CORE_PEER_ID=peer1.org2.abc.com
      - CORE_PEER_ADDRESS=peer1.org2.abc.com:10051
      - CORE_PEER_LISTENADDRESS=0.0.0.0:10051
      - CORE_PEER_CHAINCODEADDRESS=peer1.org2.abc.com:10052
      - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:10052
      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer1.org2.abc.com:10051
      - CORE_PEER_GOSSIP_BOOTSTRAP=peer0.org2.abc.com:9051
      - CORE_PEER_LOCALMSPID=Org2MSP
    volumes:
        - /var/run/:/host/var/run/
        - ../crypto-config/peerOrganizations/org2.abc.com/peers/peer1.org2.abc.com/msp:/etc/hyperledger/fabric/msp
        - ../crypto-config/peerOrganizations/org2.abc.com/peers/peer1.org2.abc.com/tls:/etc/hyperledger/fabric/tls
        - peer1.org2.abc.com:/var/hyperledger/production
    ports:
      - 10051:10051










现在我们的东西都改好了
我们来启动fabric网络

docker-compose -f docker-compose-cli.yaml up -d




我们发现报了一点小错误
abc@abc:~/workspace/fabric$ docker-compose -f docker-compose-cli.yaml up -d
WARNING: The IMAGE_TAG variable is not set. Defaulting to a blank string.
ERROR: yaml.scanner.ScannerError: mapping values are not allowed here
  in "/home/abc/workspace/fabric/base/peer-base.yaml", line 10, column 35
abc@abc:~/workspace/fabric$ docker-compose -f docker-compose-cli.yaml up -d
WARNING: The IMAGE_TAG variable is not set. Defaulting to a blank string.
WARNING: The COMPOSE_PROJECT_NAME variable is not set. Defaulting to a blank string.
ERROR: no such image: hyperledger/fabric-orderer:: invalid reference format
abc@abc:~/workspace/fabric$ docker-compose -f docker-compose-cli.yaml up -d
WARNING: The COMPOSE_PROJECT_NAME variable is not set. Defaulting to a blank string.
WARNING: The IMAGE_TAG variable is not set. Defaulting to a blank string.
ERROR: no such image: hyperledger/fabric-orderer:: invalid reference format




我们重新修改一下三个文件
把IMAGE_TAG删除掉

比如这里:

  cli:
    container_name: cli
    image: hyperledger/fabric-tools:$IMAGE_TAG

删掉后改成

  cli:
    container_name: cli
    image: hyperledger/fabric-tools
	
	
	
	
然后我们把cli的container_name改成 cli_fabric

	
	


然后我们重新看一下三个文件

# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

version: '2'

volumes:
  orderer.abc.com:
  peer0.org1.abc.com:
  peer1.org1.abc.com:
  peer0.org2.abc.com:
  peer1.org2.abc.com:

networks:
  byfn:

services:

  orderer.abc.com:
    extends:
      file:   base/docker-compose-base.yaml
      service: orderer.abc.com
    container_name: orderer.abc.com
    networks:
      - byfn

  peer0.org1.abc.com:
    container_name: peer0.org1.abc.com
    extends:
      file:  base/docker-compose-base.yaml
      service: peer0.org1.abc.com
    networks:
      - byfn

  peer1.org1.abc.com:
    container_name: peer1.org1.abc.com
    extends:
      file:  base/docker-compose-base.yaml
      service: peer1.org1.abc.com
    networks:
      - byfn

  peer0.org2.abc.com:
    container_name: peer0.org2.abc.com
    extends:
      file:  base/docker-compose-base.yaml
      service: peer0.org2.abc.com
    networks:
      - byfn

  peer1.org2.abc.com:
    container_name: peer1.org2.abc.com
    extends:
      file:  base/docker-compose-base.yaml
      service: peer1.org2.abc.com
    networks:
      - byfn

  cli:
    container_name: cli_fabric
    image: hyperledger/fabric-tools
    tty: true
    stdin_open: true
    environment:
      - GOPATH=/opt/gopath
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      #- FABRIC_LOGGING_SPEC=DEBUG
      - FABRIC_LOGGING_SPEC=INFO
      - CORE_PEER_ID=cli
      - CORE_PEER_ADDRESS=peer0.org1.abc.com:7051
      - CORE_PEER_LOCALMSPID=Org1MSP
      - CORE_PEER_TLS_ENABLED=true
      - CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.abc.com/peers/peer0.org1.abc.com/tls/server.crt
      - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.abc.com/peers/peer0.org1.abc.com/tls/server.key
      - CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.abc.com/peers/peer0.org1.abc.com/tls/ca.crt
      - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.abc.com/users/Admin@org1.abc.com/msp
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    command: /bin/bash
    volumes:
        - /var/run/:/host/var/run/
        - ./../chaincode/:/opt/gopath/src/github.com/chaincode
        - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
        - ./scripts:/opt/gopath/src/github.com/hyperledger/fabric/peer/scripts/
        - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts
    depends_on:
      - orderer.abc.com
      - peer0.org1.abc.com
      - peer1.org1.abc.com
      - peer0.org2.abc.com
      - peer1.org2.abc.com
    networks:
      - byfn











# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

version: '2'

services:

  orderer.abc.com:
    container_name: orderer.abc.com
    extends:
      file: peer-base.yaml
      service: orderer-base
    volumes:
        - ../channel-artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block
        - ../crypto-config/ordererOrganizations/abc.com/orderers/orderer.abc.com/msp:/var/hyperledger/orderer/msp
        - ../crypto-config/ordererOrganizations/abc.com/orderers/orderer.abc.com/tls/:/var/hyperledger/orderer/tls
        - orderer.abc.com:/var/hyperledger/production/orderer
    ports:
      - 7050:7050

  peer0.org1.abc.com:
    container_name: peer0.org1.abc.com
    extends:
      file: peer-base.yaml
      service: peer-base
    environment:
      - CORE_PEER_ID=peer0.org1.abc.com
      - CORE_PEER_ADDRESS=peer0.org1.abc.com:7051
      - CORE_PEER_LISTENADDRESS=0.0.0.0:7051
      - CORE_PEER_CHAINCODEADDRESS=peer0.org1.abc.com:7052
      - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7052
      - CORE_PEER_GOSSIP_BOOTSTRAP=peer1.org1.abc.com:8051
      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org1.abc.com:7051
      - CORE_PEER_LOCALMSPID=Org1MSP
    volumes:
        - /var/run/:/host/var/run/
        - ../crypto-config/peerOrganizations/org1.abc.com/peers/peer0.org1.abc.com/msp:/etc/hyperledger/fabric/msp
        - ../crypto-config/peerOrganizations/org1.abc.com/peers/peer0.org1.abc.com/tls:/etc/hyperledger/fabric/tls
        - peer0.org1.abc.com:/var/hyperledger/production
    ports:
      - 7051:7051

  peer1.org1.abc.com:
    container_name: peer1.org1.abc.com
    extends:
      file: peer-base.yaml
      service: peer-base
    environment:
      - CORE_PEER_ID=peer1.org1.abc.com
      - CORE_PEER_ADDRESS=peer1.org1.abc.com:8051
      - CORE_PEER_LISTENADDRESS=0.0.0.0:8051
      - CORE_PEER_CHAINCODEADDRESS=peer1.org1.abc.com:8052
      - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:8052
      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer1.org1.abc.com:8051
      - CORE_PEER_GOSSIP_BOOTSTRAP=peer0.org1.abc.com:7051
      - CORE_PEER_LOCALMSPID=Org1MSP
    volumes:
        - /var/run/:/host/var/run/
        - ../crypto-config/peerOrganizations/org1.abc.com/peers/peer1.org1.abc.com/msp:/etc/hyperledger/fabric/msp
        - ../crypto-config/peerOrganizations/org1.abc.com/peers/peer1.org1.abc.com/tls:/etc/hyperledger/fabric/tls
        - peer1.org1.abc.com:/var/hyperledger/production

    ports:
      - 8051:8051

  peer0.org2.abc.com:
    container_name: peer0.org2.abc.com
    extends:
      file: peer-base.yaml
      service: peer-base
    environment:
      - CORE_PEER_ID=peer0.org2.abc.com
      - CORE_PEER_ADDRESS=peer0.org2.abc.com:9051
      - CORE_PEER_LISTENADDRESS=0.0.0.0:9051
      - CORE_PEER_CHAINCODEADDRESS=peer0.org2.abc.com:9052
      - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:9052
      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org2.abc.com:9051
      - CORE_PEER_GOSSIP_BOOTSTRAP=peer1.org2.abc.com:10051
      - CORE_PEER_LOCALMSPID=Org2MSP
    volumes:
        - /var/run/:/host/var/run/
        - ../crypto-config/peerOrganizations/org2.abc.com/peers/peer0.org2.abc.com/msp:/etc/hyperledger/fabric/msp
        - ../crypto-config/peerOrganizations/org2.abc.com/peers/peer0.org2.abc.com/tls:/etc/hyperledger/fabric/tls
        - peer0.org2.abc.com:/var/hyperledger/production
    ports:
      - 9051:9051

  peer1.org2.abc.com:
    container_name: peer1.org2.abc.com
    extends:
      file: peer-base.yaml
      service: peer-base
    environment:
      - CORE_PEER_ID=peer1.org2.abc.com
      - CORE_PEER_ADDRESS=peer1.org2.abc.com:10051
      - CORE_PEER_LISTENADDRESS=0.0.0.0:10051
      - CORE_PEER_CHAINCODEADDRESS=peer1.org2.abc.com:10052
      - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:10052
      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer1.org2.abc.com:10051
      - CORE_PEER_GOSSIP_BOOTSTRAP=peer0.org2.abc.com:9051
      - CORE_PEER_LOCALMSPID=Org2MSP
    volumes:
        - /var/run/:/host/var/run/
        - ../crypto-config/peerOrganizations/org2.abc.com/peers/peer1.org2.abc.com/msp:/etc/hyperledger/fabric/msp
        - ../crypto-config/peerOrganizations/org2.abc.com/peers/peer1.org2.abc.com/tls:/etc/hyperledger/fabric/tls
        - peer1.org2.abc.com:/var/hyperledger/production
    ports:
      - 10051:10051










# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

version: '2'

services:
  peer-base:
    image: hyperledger/fabric-peer
    environment:
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      # the following setting starts chaincode containers on the same
      # bridge network as the peers
      # https://docs.docker.com/compose/networking/
      - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=${COMPOSE_PROJECT_NAME}_byfn
      - FABRIC_LOGGING_SPEC=INFO
      #- FABRIC_LOGGING_SPEC=DEBUG
      - CORE_PEER_TLS_ENABLED=true
      - CORE_PEER_GOSSIP_USELEADERELECTION=true
      - CORE_PEER_GOSSIP_ORGLEADER=false
      - CORE_PEER_PROFILE_ENABLED=true
      - CORE_PEER_TLS_CERT_FILE=/etc/hyperledger/fabric/tls/server.crt
      - CORE_PEER_TLS_KEY_FILE=/etc/hyperledger/fabric/tls/server.key
      - CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/tls/ca.crt
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    command: peer node start

  orderer-base:
    image: hyperledger/fabric-orderer
    environment:
      - FABRIC_LOGGING_SPEC=INFO
      - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0
      - ORDERER_GENERAL_GENESISMETHOD=file
      - ORDERER_GENERAL_GENESISFILE=/var/hyperledger/orderer/orderer.genesis.block
      - ORDERER_GENERAL_LOCALMSPID=OrdererMSP
      - ORDERER_GENERAL_LOCALMSPDIR=/var/hyperledger/orderer/msp
      # enabled TLS
      - ORDERER_GENERAL_TLS_ENABLED=true
      - ORDERER_GENERAL_TLS_PRIVATEKEY=/var/hyperledger/orderer/tls/server.key
      - ORDERER_GENERAL_TLS_CERTIFICATE=/var/hyperledger/orderer/tls/server.crt
      - ORDERER_GENERAL_TLS_ROOTCAS=[/var/hyperledger/orderer/tls/ca.crt]
      - ORDERER_KAFKA_TOPIC_REPLICATIONFACTOR=1
      - ORDERER_KAFKA_VERBOSE=true
      - ORDERER_GENERAL_CLUSTER_CLIENTCERTIFICATE=/var/hyperledger/orderer/tls/server.crt
      - ORDERER_GENERAL_CLUSTER_CLIENTPRIVATEKEY=/var/hyperledger/orderer/tls/server.key
      - ORDERER_GENERAL_CLUSTER_ROOTCAS=[/var/hyperledger/orderer/tls/ca.crt]
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric
    command: orderer
















然后我们启动一下

abc@abc:~/workspace/fabric$ docker-compose -f docker-compose-cli.yaml up -d
WARNING: The COMPOSE_PROJECT_NAME variable is not set. Defaulting to a blank string.
Creating peer0.org2.abc.com ... done
Creating peer1.org1.abc.com ... done
Creating peer1.org2.abc.com ... done
Creating orderer.abc.com    ... done
Creating peer0.org1.abc.com ... done
Creating cli                ... error



然后我们看下docker的container容器列表

abc@abc:~/workspace/fabric$ docker ps
CONTAINER ID        IMAGE                      COMMAND             CREATED             STATUS              PORTS                      NAMES
6ef5786be7da        hyperledger/fabric-tools   "/bin/bash"         9 seconds ago       Up 7 seconds                                   cli_fabric
f97991781758        hyperledger/fabric-peer    "peer node start"   9 minutes ago       Up 9 minutes        0.0.0.0:10051->10051/tcp   peer1.org2.abc.com
1d95b307a167        hyperledger/fabric-peer    "peer node start"   9 minutes ago       Up 9 minutes        0.0.0.0:7051->7051/tcp     peer0.org1.abc.com
eb8e2d22d111        hyperledger/fabric-peer    "peer node start"   9 minutes ago       Up 9 minutes        0.0.0.0:8051->8051/tcp     peer1.org1.abc.com
decef0055aaa        hyperledger/fabric-peer    "peer node start"   9 minutes ago       Up 9 minutes        0.0.0.0:9051->9051/tcp     peer0.org2.abc.com






我们再用一个命令看一下
docker-compose -f docker-compose-cli.yaml ps


abc@abc:~/workspace/fabric$ docker-compose -f docker-compose-cli.yaml ps
WARNING: The COMPOSE_PROJECT_NAME variable is not set. Defaulting to a blank string.
       Name              Command       State             Ports          
------------------------------------------------------------------------
cli_fabric           /bin/bash         Up                               
orderer.abc.com      orderer           Up                          
peer0.org1.abc.com   peer node start   Up       0.0.0.0:7051->7051/tcp  
peer0.org2.abc.com   peer node start   Up       0.0.0.0:9051->9051/tcp  
peer1.org1.abc.com   peer node start   Up       0.0.0.0:8051->8051/tcp  
peer1.org2.abc.com   peer node start   Up       0.0.0.0:10051->10051/tcp









然后,再看一下网络
docker network ls

abc@abc:~/workspace/fabric$ docker network ls
NETWORK ID          NAME                DRIVER              SCOPE
90213af75fe5        bridge              bridge              local
e10d5b5eebdb        fabric_byfn         bridge              local
7fb04f2c9379        host                host                local
5ffa8612ee4f        net_byfn            bridge              local
3ac4bccfcb5d        none                null                local








OK
fabric网络启动成功

 

Lich Howger
关注
  • 2
    点赞
  • 踩
  • 2
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
fabric故障汇总与解决方案
小树苗
01-09 7487
问题1：阿里云服务器bug不兼容fabric 阿里云的服务器启动会报错如下： Error: error getting endorser client for channel: endorser client failed to connect to peer0.org1.example.com:7051: failed to create new connection: connection...
Hyperledger Fabric Peer 配置解析
黑帽子技术的博客
02-23 915
Hyperledger Fabric Peer 配置解析 文中使用的 fabric 版本为 2.4.1 ...
Hyperledger Fabric1.4遇到的坑
Xiao__FengFeng的博客
03-09 6831
Hyperledger Fabric遇到的那些坑 1.生成起始区块出错 Error on outputBlock: Error writing genesis block: open ./channel-artifacts/genesis.block: no such file or director 错误原因：路径中目录如果不存在，需提前创建。 解决 mkdir channel-artifacts 2.启动容器时出错 ERROR: no such image: hyperledger/fabric-o
Docker-Compose通过文件声明默认的环境变量
weixin_30367543的博客
06-17 544
写文目的 在写本文之前，我在做一个docker-compose项目，这里需要在docker-compose.yml配置中引用到宿主机的ip，然而docker-compose并没有命令行一个输入的选项，看了些博客和官方文档，发现自己定义的如common.env中定义的键值对，只能完全当做环境变量被引用，而不是部分变量。纠结良久，又仔细看了官方文档，发现了默认的配置，docker也可用，记录作此文，备...
The DOCKER_REGISTRY variable is not set. Defaulting to a blank string.
热门推荐
LiveviL的博客
09-14 1万+
vs2017中添加Docker支持后，有时运行docker-compose,会报如下错误 The DOCKER_REGISTRY variable is not set. Defaulting to a blank string. 解决办法： 一般我电脑上重启Docker就可以了。 如果不能解决，在StackOverflow上面，提供的解决方法是： 1.以管理员身份运行Visual...
(三)Fabric2.0启动网络脚本配置剖析
01-07
(三)Fabric2.0启动网络脚本配置剖析 (四)Fabric2.0通道实践 (五)Fabric2.0 智能合约实践- 安装以及定义智能合约 (六)Fabric2.0 智能合约实践- 升级智能合约 (七)Fabric2.0智能合约实践-设置背书策略 目录1.byfn.sh2...
阿里云javasdk源码-spring-fabric-gateway:Fabric-gateway-java的Spring启动状态（https
06-06
fabric-gateway-spring-boot-starter ：一个 spring MVC 启动器。 fabric-explorer-spring-boot-starter ：一个简单的 Fabric Explorer 启动器。 如何使用 Spring Boot 配置： 首先，将以下依赖项添加到项目的pom....
hyperledger fabric 网络搭建部署
最新发布
07-04
hyperledger fabric 网络搭建部署; 1.hyperledger-fabric 介绍和资料整理 2.服务环境准备 3.安装fabric 二进制源码程序 ...6.启动配置网络节点 docker-compose启动文件 7.将组织加入通道 8.安装合约
fabric-starter:Hyperledger Fabric的入门应用程序和部署脚本
05-13
该启动程序的脚本生成加密材料和配置文件，启动网络并部署您的链码。 开发人员可以使用来调用和查询链码，探索区块和事务。 剩下的就是开发链码并将其放置在文件夹中，并将用户界面作为单页Web应用程序放置在源...
fabric-sdk-java+ springBoot 简单invoke和query引用示例
03-11
这是一个基于spingBoot的项目,通过此项目可以实现对fabric网络的简单调用,并且可以启动一个fabric网路的服务,直接在网页上调用. 搭建流程,首先需要fabric1.4的网络， 1进入-first-network目录，修改byfn.sh中...
关于Fabric的启动
chunduiyun021771的博客
12-12 567
Fabric网络提供的是联盟链服务，联盟由多个组织构成，组织中的成员提供了节点服务来维护网络，同时通过身份来进行权限管理。前面有提到过的通道概念就可以理解为一个通道（Fabric中的channel）对应一个联盟，一个通道上可以有多个组织，每个组织（Fabric中的org）有多个成员（Fabri...
搭建一个Fabric网络的步骤(启动一个Fabric网络概述)
每一个不曾起舞的日子，都是对生命的辜负
12-17 1835
1、预备网络内各项配置，Fabric网络在启动之前，需要提前生成一些用于启动的配置文件： （1）网络成员：使用cryptogen工具(配置文件cryptogen-config.yaml)，生成成员的组织结构和对应的身份证书； （2）系统通道：生成系统通道的初始配置区块文件； （3）应用通道：新建应用通道的配置，更新交易文件； （4）锚节点：新建锚节点配置更新交易文件； 我们只需要编写配置文件(crypto-config.yaml和configtx.yaml)，然后利用工具cryptogen和configt
Hyperledger Fabric 中 Gossip 数据传播协议
黑帽子技术的博客
03-01 402
Hyperledger Fabric 中 Gossip 数据传播协议 https://hyperledger-fabric.readthedocs.i...
docker-compose中的环境变量
ochinchina_cn的专栏
03-20 4675
使用docker-compose部署一个MySQL server. mysq serverl的数据库文件存放在/var/lib/mysql目录下，为了重启mysql server不至于丢失创建的数据库数据，我们需要mount一个目录到mysql server容器的/var/lib/mysql。用docker-compose创建一个mysql instance大概如下： version: '2'
Gossip 数据传播协议
phymat.nico的专栏
04-13 915
Gossip 数据传播协议 Hyperledger Fabric 通过将工作负载拆分为交易执行（背书和提交）节点和交易排序节点的方式来优化区块链网络的性能、安全性和可扩展性。对网络操作这样的分割就需要一个安全、可靠和可扩展的数据传播协议来保证数据的完整性和一致性。为了满足这个需求，Fabric 实现了 Gossip 数据传播协议 。 Gossip 协议 Peer 节点通过 gossip 协议...
Centos7 Fabric2.4 网络搭建（一）
humingwei11的博客
03-28 2882
提示：记录自己学习Fabric的过程
fabric004 fabric 核心模块----Peer模块的更为详细的介绍
水野与小太郎的博客
11-23 2423
peer模块式fabric中最重要的模块，也是fabric系统中使用最多的模块；peer模块在Fabric中被称为主节点模块，主要负责： 存储区块链数据、运行维护链码、提供对外服务接口等作用。 peer的环境变量 export set CORE_VM_ENDPOINT=unix:// /var/run/docker.sock  export set CORE_VM_DOCKER_HOS...
fabric网络伪集群部署
btqszl的博客
05-16 1678
部署一个fabric伪集群,有A、B、C三个机器分别部署A(sdk)、B(fabric集群的部分)、C(fabric集群的部分)部署中遇到一些问题：1.zookeeper部署问题每一个zookeeper节点需要知道集群中所有节点，通过ZOO_SERVERS来指定每个节点通过ZOO_MY_ID来判别ZOO_SERVERS哪个是自己，例如ZOO_MY_ID=3，则server.3为自己的节点，对于自己...
部署 Hyperledger Cello 文档
纵横四海的博客
04-20 7426
概述 Hyperledger Cello是Hyperledger下的一个子项目，其主要功能如下: 1. 管理区块链的生命周期，例如自动创建/启动/停止/删除/保持健康状态。 2. 支持定制（例如，大小，一致）区块链请求，目前主要支持Hyperledger架构。 3. 支持裸机，虚拟机，本地Docker主机，群集或Kubernetes作为工作节点。 更多的支持途中。 4. 支持异构体...
如何使用fabric-sdk-java和fabric网络交互
05-23
1. 安装并启动fabric网络。可以使用Docker Compose或Kubernetes等工具来快速设置fabric网络。 2. 配置fabric-sdk-java环境。需要下载fabric-sdk-java并设置相应的环境变量。 3. 创建SDK实例。需要创建SDK实例并...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值