Cannot create container for service peer1.org2.example.com: Conflict. 解决方案

最新推荐文章于 2024-04-12 09:39:16 发布
最新推荐文章于 2024-04-12 09:39:16 发布
阅读量4.1k 收藏 14
点赞数 8
文章标签： 运维 java php
I have a docker-compose.yaml file defining 5 services:
  • orderer.example.com
  • peer0.org1.example.com
  • peer1.org1.example.com
  • peer0.org2.example.com
  • peer1.org2.example.com

Running the

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

command results in:

Creating network "hlf_byfn" with the default driver
Creating peer1.org1.example.com ... 
Creating peer0.org2.example.com ... 
Creating peer1.org2.example.com ... 
Creating orderer.example.com ... 
Creating peer0.org1.example.com ... 
Creating peer0.org2.example.com
Creating peer1.org1.example.com
Creating peer1.org2.example.com
Creating orderer.example.com
Creating orderer.example.com ... error

ERROR: for orderer.example.com  Cannot create container for service orderer.example.com: Conflict. The container name "/orderer.example.com" is already in use by container "d6621116cf0d1ab108277893178ba29aCreating peer0.org1.example.com ... error

ERROR: for peer0.org1.example.com  Cannot create container for service peer0.org1.example.com: Conflict. The container name "/peer0.org1.example.com" is already in use by container "185c6449d163fa5593001b3Creating peer0.org2.example.com ... done

ERROR: for peer0.org1.example.com  Cannot create container for service peer0.org1.example.com: Conflict. The container name "/peer0.org1.example.com" is already in use by container "185c6449d163fa5593001b3bf9e052eee9ea365f89564a31fd84aac3c828bfbd". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for orderer.example.com  Cannot create container for service orderer.example.com: Conflict. The container name "/orderer.example.com" is already in use by container "d6621116cf0d1ab108277893178ba29a05d4e50b36143d33fb6ec1dfc472eeb8". You have to remove (or rename) that container to be able to reuse that name.
ERROR: Encountered errors while bringing up the project.

So orderer.example.com and peer0.org1.example.com could not be created. Output of docker ps :

CONTAINER ID        IMAGE                     COMMAND             CREATED              STATUS              PORTS                                              NAMES
543b2bf5df5c        hyperledger/fabric-peer   "peer node start"   About a minute ago   Up About a minute   0.0.0.0:8051->7051/tcp, 0.0.0.0:8053->7053/tcp     peer1.org1.example.com
1c652a838c3b        hyperledger/fabric-peer   "peer node start"   About a minute ago   Up About a minute   0.0.0.0:10051->7051/tcp, 0.0.0.0:10053->7053/tcp   peer1.org2.example.com
65bdfcf71517        hyperledger/fabric-peer   "peer node start"   About a minute ago   Up About a minute   0.0.0.0:9051->7051/tcp, 0.0.0.0:9053->7053/tcp     peer0.org2.example.com

docker-compose.yaml:

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

version: '2'

networks:
  byfn:

services:

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

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

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

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

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

  cli:
    container_name: cli
    image: hyperledger/fabric-tools
    tty: true
    environment:
      - GOPATH=/opt/gopath
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      - CORE_LOGGING_LEVEL=DEBUG
      - CORE_PEER_ID=cli
      - CORE_PEER_ADDRESS=peer0.org1.example.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.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
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    volumes:
        - /var/run/:/host/var/run/
        - ./../chaincode/:/opt/gopath/src/github.com/hyperledger/fabric/examples/chaincode/go
        - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
        - ./scripts:/opt/gopath/src/github.com/hyperledger/fabric/peer/scripts/
        - ./channel-artefacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artefacts
    depends_on:
      - orderer.example.com
      - peer0.org1.example.com
      - peer1.org1.example.com
      - peer0.org2.example.com
      - peer1.org2.example.com
    networks:
      - byfn

How can I determine, what went wrong, why the container name is in use already?

 
  •  
    Can you please paste your docker-compose.yaml file? 
  • added docker-compose.yaml – 

Based on the errors you provided:

ERROR: for orderer.example.com Cannot create container for service orderer.example.com: Conflict. The container name "/orderer.example.com" is already in use by container "d6621116cf0d1ab108277893178ba29aCreating peer0.org1.example.com ... error

ERROR: for peer0.org1.example.com Cannot create container for service peer0.org1.example.com: Conflict. The container name "/peer0.org1.example.com" is already in use by container "185c6449d163fa5593001b3Creating peer0.org2.example.com ... done

ERROR: for peer0.org1.example.com Cannot create container for service peer0.org1.example.com: Conflict. The container name "/peer0.org1.example.com" is already in use by container "185c6449d163fa5593001b3bf9e052eee9ea365f89564a31fd84aac3c828bfbd". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for orderer.example.com Cannot create container for service orderer.example.com: Conflict. The container name "/orderer.example.com" is already in use by container "d6621116cf0d1ab108277893178ba29a05d4e50b36143d33fb6ec1dfc472eeb8". You have to remove (or rename) that container to be able to reuse that name.

ERROR: Encountered errors while bringing up the project

I'd assume that you have stopped containers which was not removed/cleaned up from your previous executions/trials and therefore starting new containers with same names concludes to the errors above. Could you please try to run

docker ps -a

　　

to check whenever you have containers with names: peer0.org1.example.com, peer0.org1.example.com and etc...?

At any case you can try to run

docker ps -qa | xargs docker stop

　　

docker ps -qa | xargs docker rm

　　

and then try to startup your network again:

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

　　

Docker compose command :Cannot create container for service nsqlookupd: Conflict.
飞越蓝天的专栏
04-06 2428
今天使用Docker中的compose文件来启动NSQ服务时，提示报错：Cannot create container for service nsqlookupd: Conflict…如下所示： 找了好久，找到一种快速解决办法： docker system prune
Chrome的启动参数
Criss@陈磊
02-23 5542
List of Chromium Command Line Switches Condition Explanation --[1]⊗ Classic, non-material, mode for the |kTopChromeMD| switch.↪ --0⊗ Value of the --profiler-timing flag that will disable timin...
ERROR: for xxx Cannot create container for service xxx: No command specified
yuchendejiyi的博客
09-16 1万+
问题： 问题描述：​​​​​​​
ERROR: Cannot create container for service **: Conflict. The container name** is already in use by c
m0_52896752的博客
03-08 1842
ERROR: Cannot create container for service **: Conflict. The container name** is already in use by c
Cannot create container for service mongo: Post “http://unix/filesharing/share“: context deadline e
Tech My Life
12-13 1545
Win10+Docker使用docker-compose安装yapi报错如下： PS D:\Docker\docker-yapi\mongo> cd .. PS D:\Docker\docker-yapi> docker-compose up Creating docker-yapi_mongo_1 ... error ER...
Hyperledger Fabric1.4 多机部署（尚有问题暂未解决）
盲人摸象
07-08 2835
参考教程（主）：https://www.cnblogs.com/cbkj-xd/p/11067814.html作者触不可及，出处https://www.cnblogs.com/cbkj-xd/ 非常推荐！ 其他参考教程：https://segmentfault.com/a/1190000021387316https://www.cnblogs.com/studyzy/p/7237287.html 本文根据上述参考教程的步骤进行实验操作，截图为自己的操作截图，有问题和我自己修改的部分用蓝色标注。 内容如..
kubeadm 以 containerd & cri-docker 作为容器运行时，部署1.26.9版本的kubernetes集群
刘某的博客
04-12 858
本文采用 kubeadm，以 containerd & cri-docker 作为容器运行时，部署 calico 网络模式的k8s集群
RAC: Frequently Asked Questions [ID 220970.1]
11-22 1626
RAC: Frequently Asked Questions [ID 220970.1]Applies to: Oracle Server - Enterprise Edition - Version 9....
历年计算机科学领域中各大顶会的获奖文章 ICCV、AAAI、CVPR...
ghw15221836342的博客
01-12 5059
Original address: https://jeffhuang.com/best_paper_awards.html By Conference:   AAAI   ACL   CHI   CIKM   CVPR   FOCS   FSE   ICCV   ICML   ICSE   IJCAI   INFOCOM   KDD   MOBICOM   NSDI   OSDI   PLDI...
error getting endorser client for channel: endorser client failed to connect to peer1.org1.example.c
sloan1227的博客
03-22 1541
问题5：error getting endorser client for channel: endorser client failed to connect to peer1.org1.example.com:7051: failed to create new connection: context deadline exceeded peer1.org1 failed to join the channel, Retry after 3 seconds
创建新Docker容器时出现“The container name "/xxx" is already in use by container xxxxxxxxxxx...”问题的解决办法
热门推荐
iw1210的专栏
12-01 7万+
创建新Docker容器时出现“The container name "/xxx" is already in use by container xxxxxxxxxxx...”问题的解决办法 详细错误提示： /usr/bin/docker-current: Error response from daemon: Conflict. The container name "/xxx" is alre...
使用Hyperledger fabric1.4.4的fabric-samples搭建多链环境
weixin_41303815的博客
08-12 1305
愿景 网络部署4个组织 每个组织下两个节点 peer0.org1 端口号：7051 peer1.org1 端口号：8051 peer0.org2 端口号：9051 peer1.org2 端口号：10051 peer0.org3 端口号：11051 peer1.org3 端口号：12051 peer0.org4 端口号：13051 peer1.org4 端口号：14051 需要修改的 文件 1 crypto-config.yaml文件中 添加新组织配置信息 生成数字证书和密钥 2 configtx.yaml文
Fabric部署多机版本
sanqima的专栏
08-04 862
Fabric v1.4.3的First-network默认是单机版本，采用solo模式。下面介绍其多机版本的部署方法。 1、描述 2、软件环境     fabric-samples v1.4.3     fabric v1.4.3     fabric ca v1.4.3     Ubuntu 16.04 3、将First-network复制一份,重命名为one,然后精简one文件夹 3.1 精简first-network cd $GOPATH/src/github.com/hyperledger/
ERROR: for orderer.example.com Cannot create container for service orderer.example.com: Conflict. T
weixin_43902997的博客
11-04 1002
./network.sh up 搭建fabric2.2网络时遇到的问题，留一个记录。 根据提示，显示已经存在peer节点，这是上次跑fabric1.x版本遗留的问题。 sudo docker stop $(sudo docker ps -aq) 可看到结果： 所以需要关闭这些容器 sudo docker rm $(sudo docker ps -aq) 再次执行 ./network.sh up 可以看到结果是成功的 ...
Fabric1.4.0网络搭建_自动化脚本实现
qq_22016915的博客
08-02 873
1.安装linux系统 2.安装docker 3.
version: '2' volumes: orderer.example.com: peer0.org1.example.com: peer1.org1.example.com: peer0.org2.example.com: peer1.org2.example.com: networks: test: services: orderer.example.com: extends: file: base/docker-compose-base.yaml service: orderer.example.com container_name: orderer.example.com networks: - test ERROR: yaml.parser.ParserError: while parsing a block mapping in "./docker-compose-cli.yaml", line 1, column 1 expected <block end>, but found '<block mapping start>' in "./docker-compose-cli.yaml", line 13, column 2
最新发布
03-20
<think>好的，用户遇到了Docker Compose的YAML解析错误，需要帮助解决。首先，我得回想一下常见的YAML格式错误。YAML对缩进和语法结构非常敏感，尤其是在使用块映射（block mapping）时。用户提供的错误信息提到在解析块映射时遇到了问题，预期是块结束符，但发现了序列开始符。这可能是因为缩进不正确或者冒号后面缺少空格。 查看用户提供的引用，比如引用[1]和[2]，错误出现在不同的行号，但都是关于块映射解析错误。常见的错误原因包括： 1. **缩进问题**：YAML使用空格缩进，通常两个或四个空格，不能使用Tab键。如果缩进不正确，解析器会报错。 2. **冒号后缺少空格**：键值对中的冒号后面必须有一个空格，例如`key: value`，如果写成`key:value`会出错。 3. **不正确的列表格式**：在块序列中，每个列表项前应有正确的缩进和短横线，且对齐一致。 4. **错误的嵌套结构**：比如在映射中错误地嵌套了序列，或者缩进层次不正确。 接下来需要具体分析用户的docker-compose.yml文件结构。根据错误信息中的行号，比如第4行第5列和第11行第8列，推测问题可能出在这些行的缩进或语法上。例如，可能在某个服务定义下，缩进不正确，或者列表项没有正确对齐。 另外，用户提到引用[4]中的情况，尝试运行Jar文件但失败，可能是因为命令格式不正确。在YAML中，多行命令需要使用管道符号或正确的缩进，例如： ```yaml command: > java -jar myapp.jar ``` 或者使用列表格式： ```yaml command: ["java", "-jar", "myapp.jar"] ``` 如果命令的格式不正确，也会导致解析错误。 可能的解决方案步骤： 1. **检查缩进**：确保所有层级的缩进一致，使用空格而非Tab。 2. **检查冒号后的空格**：每个键值对的冒号后必须有一个空格。 3. **验证YAML结构**：使用在线YAML验证工具或`yamllint`工具检查文件。 4. **查看具体错误行**：根据报错信息定位到具体行和列，检查该处的语法。 5. **处理多行命令**：确保命令部分正确使用多行格式或列表形式。 例如，如果错误出现在第11行第8列，可能是在某个服务的environment或volumes部分，列表项的缩进不正确。正确的写法应该是： ```yaml services: app: image: myapp:latest environment: - ENV_VAR1=value1 - ENV_VAR2=value2 ``` 这里，每个环境变量前应有短横线和空格，并且缩进正确。如果缩进不足或格式错误，解析器会报错。 总结，用户需要逐步检查YAML文件的语法，特别是缩进、冒号后的空格以及列表项的结构。使用验证工具可以快速定位问题。此外，注意特殊字符如Tab的存在，替换为空格。</think>针对Docker Compose的YAML解析错误问题，以下是分步解决方案： --- ### **1. 定位错误位置** 根据报错信息中的行号和列号（例如`./docker-compose.yml, line 11, column 8`），直接定位到文件中的具体位置。例如： ```yaml services: app: image: nginx ports: # 假设错误出现在此行附近 - "8080:80" # 行11，列8 ``` --- ### **2. 检查基础语法问题** #### **缩进问题** - **错误示例**（使用Tab缩进）： ```yaml services: app: # 使用了Tab ``` - **修复方法**：替换为空格（推荐2或4空格）[^1][^2]。 #### **冒号后缺少空格** - **错误示例**： ```yaml environment:KEY=value # 冒号后无空格 ``` - **修复方法**： ```yaml environment: KEY=value # 冒号后加空格 ``` #### **列表格式错误** - **错误示例**（短横线未对齐或缺少空格）： ```yaml ports: -"8080:80" # 短横线后缺少空格 ``` - **修复方法**： ```yaml ports: - "8080:80" # 短横线后加空格并正确缩进 ``` --- ### **3. 验证复杂结构** #### **多行命令** - **错误示例**（未使用正确格式）： ```yaml command: java -jar app.jar --debug # 多行参数可能引发解析歧义 ``` - **修复方法**（使用列表或管道符）： ```yaml command: ["java", "-jar", "app.jar", "--debug"] # 列表形式 ``` 或 ```yaml command: > # 多行文本 java -jar app.jar --debug ``` #### **环境变量嵌套** - **错误示例**（缩进不匹配）： ```yaml environment: - DEBUG: true # 短横线与键值对混合错误 ``` - **修复方法**： ```yaml environment: DEBUG: "true" # 直接键值对 ``` 或 ```yaml environment: - DEBUG=true # 列表项格式 ``` --- ### **4. 使用工具验证** 安装`yamllint`工具检查语法： ```bash # 安装工具 pip install yamllint # 检查文件 yamllint docker-compose.yml ``` 工具会直接标记错误位置和类型，例如： ``` docker-compose.yml 11:8 error syntax error: expected <block end>, but found '<block sequence start>' ``` --- ### **5. 完整修复示例** **错误文件片段**： ```yaml services: app: # 错误：未缩进 image:nginx # 错误：冒号后无空格 ports: - "8080:80" ``` **修复后**： ```yaml services: app: image: nginx # 冒号后加空格 ports: - "8080:80" # 正确缩进 ``` --- ### **相关问题** 1. 如何避免YAML文件中的缩进错误？ 2. Docker Compose中`environment`的两种写法有何区别？ 3. YAML多行字符串的`|`和`>`符号有什么区别？ --- 通过逐步检查缩进、冒号格式和列表对齐，可解决大多数YAML解析错误。若问题持续，建议粘贴文件片段到[YAML在线验证器](https://yamlvalidator.com)进一步调试[^3][^4]。
评论 4
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值