【Hyperledger Fabric 开发学习3.5】 docker-compose 文件解析

已于 2023-07-08 16:26:28 修改
阅读量105 收藏
点赞数
分类专栏： hyperledger fabric 文章标签： fabric 学习 docker
于 2023-07-01 19:31:30 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_45603902/article/details/131493101
版权

编写 orderer 节点 docker-compose 文件

version: '2.0'

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

network:
  testwork
  
services:
  orderer.example.com:
    image: hyperledger/fabric-orderer:2.0
    container_name: orderer0.example.com
    environment:
        - FABRIC_LOGGING_SPEC=INFO
        - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0 # default: 127.0.0.1
        - ORDERER_GENERAL_LISTENPORT=7050
        - ORDERER_GENERAL_GENESISMETHOD=file # default: provisional
        - ORDERER_GENERAL_BOOTSTRAPFILE=/etc/hyperledger/fabric/orderer.genesis.block # by default, all materials should be put under $FABRIC_CFG_PATH, which defaults to /etc/hyperledger/fabric
        - ORDERER_GENERAL_LOCALMSPID=OrdererMSP # default: DEFAULT
        - ORDERER_GENERAL_LOCALMSPDIR=/etc/hyperledger/fabric/msp
       # enabled TLS
        - ORDERER_GENERAL_TLS_ENABLED=true # default: false
        - ORDERER_GENERAL_TLS_PRIVATEKEY=/etc/hyperledger/fabric/tls/server.key
        - ORDERER_GENERAL_TLS_CERTIFICATE=/etc/hyperledger/fabric/tls/server.crt
        - ORDERER_GENERAL_TLS_ROOTCAS=[/etc/hyperledger/fabric/tls/ca.crt]
        - ORDERER_GENERAL_CLUSTER_CLIENTPRIVATEKEY=/etc/hyperledger/fabric/tls/server.key
        - ORDERER_GENERAL_CLUSTER_CLIENTCERTIFICATE=/etc/hyperledger/fabric/tls/server.crt
        - ORDERER_GENERAL_CLUSTER_ROOTCAS=[/etc/hyperledger/fabric/tls/ca.crt]
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric
    command: orderer
    volumes:
      - ./channel-artifacts/orderer.genesis.block:/etc/hyperledger/fabric/orderer.genesis.block
      - ./crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/msp:/etc/hyperledger/fabric/msp
      - ./crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/tls/:/etc/hyperledger/fabric/tls
      - orderer.medical.com: /var/hyperledger/production/orderer
    ports:
      - "7050:7050"
    network:
     testwork

peer0.org1.example.com:
  image: hyperledger/fabric-peer:2.0
  container_name: peer0.org1.example.com
  environment:
    #- CORE_PEER_ADDRESSAUTODETECT=false
    - CORE_VM_ENDPOINT=unix///host/var/docker.sock  
    - CORE_PEER_ID=peer0.org1.example.com
    - CORE_PEER_ADDRESS=peer0.org1.example.com:7051
    - CORE_PEER_LISTENADDRESS=0.0.0.0:7051
    - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7052
    - CORE_PEER_CHAINCODEADDRESS=peer0.org1.example.com:7052
    - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org1.example.com:7061
    - CORE_PEER_GOSSIP_BOOTSTRAP=peer0.org1.example.com:7051
    - CORE_PEER_LOCALMSPID=Org1MSP
    - FABRIC_LOGGING_SPEC=INFO
    #- FABRIC_LOGGING_SPEC=INFO # info:core.chaincode=debug
    - CORE_PEER_TLS_ENABLED=true
    - CORE_PEER_GOSSIP_USELEADERELECTION=true
    - CORE_PEER_GOSSIP_ORGLEADER=false  # whether this node is the org leader, default to 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
    - core_CHAINCODE_EXECUTETIMEOUT=300ms
  working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
  command: peer node start
  volumes:
      - /var/run/:/host/var/run/
      - ./crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/msp:/etc/hyperledger/fabric/msp
      - ./crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls:/etc/hyperledger/fabric/tls
      - peer0.org1.example.com:/var/hyperledger/production
  ports:
      - 7051:7051
      - 7052:7052
      - 7053:7053
  network:
    testwork

peer1.org1.example.com:
  image: hyperledger/fabric-peer:2.0
  container_name: peer1.org1.example.com
  environment:
    #- CORE_PEER_ADDRESSAUTODETECT=false
    - CORE_VM_ENDPOINT=unix///host/var/docker.sock  
    - CORE_PEER_ID=peer1.org1.example.com
    - CORE_PEER_ADDRESS=peer1.org1.example.com:7061
    - CORE_PEER_LISTENADDRESS=0.0.0.0:7061
    - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7062
    - CORE_PEER_CHAINCODEADDRESS=peer1.org1.example.com:7062
    - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer1.org1.example.com:70561
    - CORE_PEER_GOSSIP_BOOTSTRAP=peer1.org1.example.com:7051
    - CORE_PEER_LOCALMSPID=Org1MSP
    - FABRIC_LOGGING_SPEC=INFO
    #- FABRIC_LOGGING_SPEC=INFO # info:core.chaincode=debug
    - CORE_PEER_TLS_ENABLED=true
    - CORE_PEER_GOSSIP_USELEADERELECTION=true
    - CORE_PEER_GOSSIP_ORGLEADER=false  # whether this node is the org leader, default to 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
    - core_CHAINCODE_EXECUTETIMEOUT=300ms
  working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
  command: peer node start
  volumes:
      - /var/run/:/host/var/run/
      - ./crypto-config/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/msp:/etc/hyperledger/fabric/msp
      - ./crypto-config/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/tls:/etc/hyperledger/fabric/tls
      - peer1.org1.example.com:/var/hyperledger/production
  ports:
      - 7061:7061
      - 7062:7062
      - 7063:7063
  network:
    testwork

peer0.org2.example.com:
  image: hyperledger/fabric-peer:2.0
  container_name: peer0.org2.example.com
  environment:
    #- CORE_PEER_ADDRESSAUTODETECT=false
    - CORE_VM_ENDPOINT=unix///host/var/docker.sock  
    - CORE_PEER_ID=peer0.org2.example.com
    - CORE_PEER_ADDRESS=peer0.org2.example.com:8051
    - CORE_PEER_LISTENADDRESS=0.0.0.0:8051
    - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:8052
    - CORE_PEER_CHAINCODEADDRESS=peer0.org2.example.com:8052
    - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org2.example.com:8061
    - CORE_PEER_GOSSIP_BOOTSTRAP=peer0.org2.example.com:8051
    - CORE_PEER_LOCALMSPID=Org2MSP
    - FABRIC_LOGGING_SPEC=INFO
    #- FABRIC_LOGGING_SPEC=INFO # info:core.chaincode=debug
    - CORE_PEER_TLS_ENABLED=true
    - CORE_PEER_GOSSIP_USELEADERELECTION=true
    - CORE_PEER_GOSSIP_ORGLEADER=false  # whether this node is the org leader, default to 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
    - core_CHAINCODE_EXECUTETIMEOUT=300ms
  working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
  command: peer node start
  volumes:
      - /var/run/:/host/var/run/
      - ./crypto-config/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/msp:/etc/hyperledger/fabric/msp
      - ./crypto-config/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls:/etc/hyperledger/fabric/tls
      - peer0.org2.example.com:/var/hyperledger/production
  ports:
      - 8051:8051
      - 8052:8052
      - 8053:8053
  network:
    testwork

peer1.org2.example.com:
  image: hyperledger/fabric-peer:2.0
  container_name: peer1.org2.example.com
  environment:
    #- CORE_PEER_ADDRESSAUTODETECT=false
    - CORE_VM_ENDPOINT=unix///host/var/docker.sock  
    - CORE_PEER_ID=peer1.org2.example.com
    - CORE_PEER_ADDRESS=peer1.org2.example.com:8061
    - CORE_PEER_LISTENADDRESS=0.0.0.0:8061
    - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:8062
    - CORE_PEER_CHAINCODEADDRESS=peer1.org2.example.com:8062
    - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer1.org2.example.com:8051
    - CORE_PEER_GOSSIP_BOOTSTRAP=peer1.org2.example.com:8051
    - CORE_PEER_LOCALMSPID=Org2MSP
    - FABRIC_LOGGING_SPEC=INFO
    #- FABRIC_LOGGING_SPEC=INFO # info:core.chaincode=debug
    - CORE_PEER_TLS_ENABLED=true
    - CORE_PEER_GOSSIP_USELEADERELECTION=true
    - CORE_PEER_GOSSIP_ORGLEADER=false  # whether this node is the org leader, default to 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
    - core_CHAINCODE_EXECUTETIMEOUT=300ms
  working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
  command: peer node start
  volumes:
      - /var/run/:/host/var/run/
      - ./crypto-config/peerOrganizations/org2.example.com/peers/peer1.org2.example.com/msp:/etc/hyperledger/fabric/msp
      - ./crypto-config/peerOrganizations/org2.example.com/peers/peer1.org2.example.com/tls:/etc/hyperledger/fabric/tls
      - peer1.org2.example.com:/var/hyperledger/production
  ports:
      - 8061:8061
      - 8062:8062
      - 8063:8063
  network:
    testwork

cli1:
  image: hyperledger/fabric-tools:2.0
  stdin_open: true
  container_name: cli
  tty: true
  depends_on:
    - peer0.org1.example.com
    - peer1.org1.example.com
    - peer0.org2.example.com
    - peer1.org2.example.com
  environment:
    - GOPATH=/opt/gopath
    - CORE_VM_ENDPOINT=unix///host/var/docker.sock
    - FABRIC_LOGGING_SPEC=INFO
    - CORE_PEER_ID=cli
    - CORE_PEER_ADDRESS=peer0.org1.example.com:7051 # default to operate on peer0.org1
    - CORE_PEER_LOCALMSPID=Org1MSP
    - CORE_PEER_TLS_ENABLED=true  # to enable TLS, change to true
    - CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt
    - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key
    - CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt
    - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
  volumes:
    - /var/run/:/host/var/run/
    - ../chaincode/go/:/opt/gopath/src/github.com/hyperledger/multiple-deployment/chaincode/go 
    - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
    - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts    
  working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
  command: /bin/bash
  network:
    testwork

cli2:
  image: hyperledger/fabric-tools:2.0
  stdin_open: true
  container_name: cli2
  tty: true
  depends_on:
    - peer0.org1.example.com
    - peer1.org1.example.com
    - peer0.org2.example.com
    - peer1.org2.example.com
  environment:
    - GOPATH=/opt/gopath
    - CORE_VM_ENDPOINT=unix///host/var/docker.sock
    - FABRIC_LOGGING_SPEC=INFO
    - CORE_PEER_ID=cli
    - CORE_PEER_ADDRESS=peer1.org1.example.com:7061 # default to operate on peer0.org1
    - CORE_PEER_LOCALMSPID=Org1MSP
    - CORE_PEER_TLS_ENABLED=true  # to enable TLS, change to true
    - CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/tls/server.crt
    - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/tls/server.key
    - CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/tls/ca.crt
    - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
  volumes:
    - /var/run/:/host/var/run/
    - ../chaincode/go/:/opt/gopath/src/github.com/hyperledger/multiple-deployment/chaincode/go 
    - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
    - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts    
  working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
  command: /bin/bash
  network:
    testwork

cli3:
  image: hyperledger/fabric-tools:2.0
  stdin_open: true
  container_name: cli3
  tty: true
  depends_on:
    - peer0.org1.example.com
    - peer1.org1.example.com
    - peer0.org2.example.com
    - peer1.org2.example.com
  environment:
    - GOPATH=/opt/gopath
    - CORE_VM_ENDPOINT=unix///host/var/docker.sock
    - FABRIC_LOGGING_SPEC=INFO
    - CORE_PEER_ID=cli
    - CORE_PEER_ADDRESS=peer0.org2.example.com:8051 # default to operate on peer0.org1
    - CORE_PEER_LOCALMSPID=Org2MSP
    - CORE_PEER_TLS_ENABLED=true  # to enable TLS, change to true
    - CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/server.crt
    - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/server.key
    - CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt
    - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp
  volumes:
    - /var/run/:/host/var/run/
    - ../chaincode/go/:/opt/gopath/src/github.com/hyperledger/multiple-deployment/chaincode/go 
    - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
    - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts    
  working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
  command: /bin/bash
  network:
    testwork

cli14:
  image: hyperledger/fabric-tools:2.0
  stdin_open: true
  container_name: cli4
  tty: true
  depends_on:
    - peer0.org1.example.com
    - peer1.org1.example.com
    - peer0.org2.example.com
    - peer1.org2.example.com
  environment:
    - GOPATH=/opt/gopath
    - CORE_VM_ENDPOINT=unix///host/var/docker.sock
    - FABRIC_LOGGING_SPEC=INFO
    - CORE_PEER_ID=cli4
    - CORE_PEER_ADDRESS=peer1.org2.example.com:8061 # default to operate on peer0.org1
    - CORE_PEER_LOCALMSPID=Org2MSP
    - CORE_PEER_TLS_ENABLED=true  # to enable TLS, change to true
    - CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer1.org2.example.com/tls/server.crt
    - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer1.org2.example.com/tls/server.key
    - CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer1.org2.example.com/tls/ca.crt
    - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp
  volumes:
    - /var/run/:/host/var/run/
    - ../chaincode/go/:/opt/gopath/src/github.com/hyperledger/multiple-deployment/chaincode/go 
    - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
    - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts    
  working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
  command: /bin/bash
  network:
    testwork

https://www.bilibili.com/video/BV1H8411Y74S/?spm_id_from=333.788&vd_source=de1585eb7b5cc18db8bc86435eb81c0f
https://my.oschina.net/j4love/blog/5454098

Mory_Herbert
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
docker-compose安装包
12-19
Docker-Compose运行目录下的所有文件（docker-compose.yml，extends文件或环境变量文件等）组成一个工程，若无特殊指定工程名即为当前目录名。一个工程当中可包含多个服务，每个服务中定义了容器运行的镜像、参数、...
docker-compose-linux-x86_64
09-21
Docker-Compose运行目录下的所有文件（docker-compose.yml，extends文件或环境变量文件等）组成一个工程，若无特殊指定工程名即为当前目录名。一个工程当中可包含多个服务，每个服务中定义了容器运行的镜像、参数、...
Hyperledger Fabric 应用实战(6)-- docker-compose编写
weixin_43274469的博客
03-04 379
编写fabric网络容器节点的 docker-compose。
深入浅出之Docker Compose详解
热门推荐
qq_43649937的博客
06-06 2万+
docker, 云原生
Hyperledger Fabric 部署
段丛磊
08-10 1547
Hyperledger Fabric 部署 Hyperledger Fabric需要使用Docker、Go环境。 Docker环境安装 Docker环境安装 直接查看这一篇，安装好之后将当前用户非root添加到Docker用户组中 #创建docker用户组 sudo groupadd docker #将当前用户添加到docker用户组 sudo usermod -aG docker...
Hyperledger Fabric 2.x 单机部署多节点网络
qq_45469783的博客
08-03 5986
本博客主要记录搭建一个3个排序节点、4个组织的每个组织各2个节点的fabric区块链网络 单机部署多节点网络1、相关环境的安装与配置2、生成相关的证书文件3、生成相关的通道配置文件4、生成docker-compose.yaml的启动文件 1、相关环境的安装与配置 go、docker、docker-compose，fabric的相关docker镜像、官方的fabric-samples文件、相关fabric二进制文件，具体配置之后补充 2、生成相关的证书文件 1）将下面的内容写入到crypto-config.y
Hyperledger Fabric配置文件解析
Lee_JH2018的博客
05-08 442
crypto-config.yaml:用于配置网络中的加密材料，例如证书、密钥等。 configtx.yaml :用于配置Fabric的创世区块和通道，包括定义组织、节点、策略、订购服务等信息。
Hyperledger Fabric 入门笔记（三）Fabric V2.5 环境搭建
sbsy123456的博客
06-20 3590
本文基于个人经验，参考相关博客，分享自己在搭建Fabric环境的步骤、问题和解决方法等，希望对大家的入门有帮助。
深入理解hyperledger fabric-1.4环境搭建的详细过程
草根工厂——技术虐我千百遍，我依然待你如初恋
07-04 2万+
1、导言： 为了学习fabric底层运行原理，这两天基于fabric 1.4版本手动部署了一个多机网络，期间遇到了很多各种各样的问题，同时也一个一个解决了，最终成功把多机fabric网络部署起来，也进行了一些简单交易测试。整个部署过程加深了本人的fabric网络的认识，再次特地把整个过程记录下来，方便以后复习；另外希望能帮助到有类似需求的人们。 2、准备工作 知识准备 ...
Hyperledger Fabric 1.4.6 多机器集群部署
J2633500154的博客
11-23 1005
Hyperledger Fabric 1.4.6 多机器集群部署（亲测有效，保姆级教程）
Hyperledger Fabric相关文件解析
weixin_30362801的博客
07-08 354
1相关文件说明 这一部分涉及相关配置文件的解析， 网络的启动涉及到多个文件，本文按以下顺序进行分析： . ├── base │ ├── docker-compose-base.yaml #1 │ └── peer-base.yaml #2 ├── channel-artifacts ├── configtx.yaml #5 ├── crypto-config.ya...
Docker-compose 教程全集 PDF 53页
07-07
Docker-Compose运行目录下的所有文件（docker-compose.yml，extends文件或环 境变量文件等）组成一个工程，若无特殊指定工程名即为当前目录名。一个工程当中可包含多个服务， 每个服务中定义了容器运行的镜像，参数...
docker-compose-maven-plugin：使用Maven运行docker-compose
02-03
Docker Compose Maven插件 ... < artifactId>docker-compose-maven-plugin $VERSION 关于 Maven插件，用于通过Maven运行基本的docker-compose命令。 它可以用作Maven生命周期的一部分，也可以用作将do
podman-compose:使用podman运行docker-compose.yml的脚本
05-12
Podman撰写带有后端的 docker-compose的实现。 该项目的主要目标是能够未经修改且无根地运行docker-compose.yml 。 该项目旨在为docker-compose提供docker-compose替换，并且在某些情况下非常有用，因为： 可以无根...
编程学习之路：从零到一的成长指南
最新发布
KsuferNotes
07-22 288
在当今数字化时代，编程技能已经成为许多人职业发展的重要组成部分。不论你是已经在IT业从业多年的老手，还是刚刚起步的编程新手，这篇博客将带你走过编程学习的每一个重要阶段，从而顺利完成从零到一的华丽转变。
昇思25天学习打卡营第14天|LLM-文本解码原理--以MindNLP为例
wwt72的博客
07-17 935
限制输出序列的最大长度为50个token。top-p=0.95，top-p采样表示在每一步生成token时，只从概率分布中累计概率达到95%的token中进行采样，有助于保持生成文本的流畅性和质量，同时允许一些低概率的token被选中，从而增加多样性。表示禁用了top-k采样，因为在top-k采样中，通常是从概率最高的k个token中随机选择一个token作为下一个输出，而这里设置为0表示不限制token的选择，实际上这将等同于使用 softmax 概率分布直接进行采样。这有助于提高生成文本的多样性。
kubernetes学习日志（七）
qq_47037022的博客
07-18 618
本文记录了service管理，ingress管理，Dashboard管理插件，集群鉴权策略，角色与全局角色，赋权与全局角色赋权。
纯前端小游戏，4096小游戏，有音效，Html5，可学习使用
m0_62996549的博客
07-18 549
【代码】纯前端小游戏，4096小游戏，有音效，Html5，可学习使用。
source /etc/profile mkdir -p /home/ubuntu/gopath/src/github.com/hyperledger cd /home/ubuntu/gopath/src/github.com/hyperledger cp /resource/docker-compose /usr/local/bin chmod +x /usr/local/bin/docker-compose cp /resource/fabric-samples.tar.gz /home/ubuntu/gopath/src/github.com/hyperledger cd /home/ubuntu/gopath/src/github.com/hyperledger tar -xf ./fabric-samples.tar.gz source /etc/profile cd /home/ubuntu/gopath/src/github.com/hyperledger/fabric-samples/scripts ./bootstrap.sh 1.4.0 1.4.0 0.4.14 cd /home/ubuntu/gopath/src/github.com/hyperledger/fabric-samples/first-network ./byfn.sh up -s couchdb docker-compose -f docker-compose-cli.yaml -f docker-compose-couch.yaml -f docker-compose-kafka.yaml start ../bin/configtxgen -profile TwoOrgsChannel -outputCreateChannelTx channel-artifacts/test.tx -channelID test
06-07
14. 执行 `docker-compose -f docker-compose-cli.yaml -f docker-compose-couch.yaml -f docker-compose-kafka.yaml start` 命令，启动 Fabric 网络中的 Docker 容器； 15. 执行 `../bin/configtxgen -profile ...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值