Docker Compose容器名冲突：期望提示容器已更新而非报错

问题背景 #

我写了docker-compose.yml用来运行本地拉取的prod镜像，同时包含mysql、phpmyadmin服务。执行docker-compose up -d时触发容器名重复的冲突报错，但我希望系统能像测试环境那样：自动拉取镜像新版本，检查各服务状态，已运行则提示up-to-date，未运行则自动创建容器。

docker-compose.yml

version: '3.3'

services:
  app-prod:
    image: prod:1.0
    container_name: app-prod
    ports:
      - "81:80"
    links:
      - db-prod
    depends_on:
      - db-prod
      - phpmyadmin-prod

  db-prod:
    image: mysql:8
    container_name: db-prod
    environment:
      - MYSQL_ROOT_PASSWORD=secret
      - MYSQL_DATABASE=laravel
      - MYSQL_USER=user
      - MYSQL_PASSWORD=secret
    volumes:
      - db-prod:/var/lib/mysql

  phpmyadmin-prod:
    image: phpmyadmin/phpmyadmin:5.0.1
    restart: always
    environment:
      PMA_HOST: db-prod
    container_name: phpmyadmin-prod
    ports:
      - "5001:80"

volumes:
  db-prod:

报错信息 #

Creating phpmyadmin-prod ... error
Creating db-prod         ... 

ERROR: for phpmyadmin-prod  Cannot create container for service phpmyadmin: Conflict. The container name "/phpmyadmin-prod" is already in use by container "5a52b27b64f7302bccb1c3a0eaeca8a33b3dfee5f1a279f6a809695Creating db-prod         ... error

ERROR: for db-prod  Cannot create container for service db: Conflict. The container name "/db-prod" is already in use by container "5d01c21efafa757008d1b4dbcc8d09b4341ac1457a0ca526ee57873cd028cf2b". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for phpmyadmin  Cannot create container for service phpmyadmin: Conflict. The container name "/phpmyadmin-prod" is already in use by container "5a52b27b64f7302bccb1c3a0eaeca8a33b3dfee5f1a279f6a809695f482500a9". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for db  Cannot create container for service db: Conflict. The container name "/db-prod" is already in use by container "5d01c21efafa757008d1b4dbcc8d09b4341ac1457a0ca526ee57873cd028cf2b". You have to remove (or rename) that container to be able to reuse that name.
ERROR: Encountered errors while bringing up the project.
Error: No such container: app-prod
Error: No such container: app-prod

测试环境正常输出 #

db-stage is up-to-date
phpmyadmin-stage is up-to-date
Creating app-stage ... done

解决方案 #

1. 先清理冲突容器 #

冲突根源是指定的容器名已经被现有容器占用，先停止并删除这些容器：

# 停止冲突容器
docker stop db-prod phpmyadmin-prod
# 删除冲突容器
docker rm db-prod phpmyadmin-prod

如果这些容器是通过当前compose文件创建的，也可以用一键命令清理：

docker-compose down

2. 调整compose配置实现期望行为 #

要实现“自动检查状态、拉取新镜像、按需创建容器”的效果，核心是移除手动指定的容器名，让Compose自动管理：

• 删除每个服务下的container_name字段：Compose默认会生成项目名_服务名_序号格式的唯一容器名，避免手动命名导致的冲突，同时支持自动识别服务状态。

修改后的docker-compose.yml：

version: '3.3'

services:
  app-prod:
    image: prod:1.0
    ports:
      - "81:80"
    links:
      - db-prod
    depends_on:
      - db-prod
      - phpmyadmin-prod

  db-prod:
    image: mysql:8
    environment:
      - MYSQL_ROOT_PASSWORD=secret
      - MYSQL_DATABASE=laravel
      - MYSQL_USER=user
      - MYSQL_PASSWORD=secret
    volumes:
      - db-prod:/var/lib/mysql

  phpmyadmin-prod:
    image: phpmyadmin/phpmyadmin:5.0.1
    restart: always
    environment:
      PMA_HOST: db-prod
    ports:
      - "5001:80"

volumes:
  db-prod:

3. 执行正确的启动流程 #

先拉取最新镜像，再启动服务，Compose会自动处理状态：

# 拉取各服务的最新镜像
docker-compose pull
# 后台启动服务，自动检查状态并按需创建/更新
docker-compose up -d

执行后就能得到和测试环境类似的输出，比如：

db-prod is up-to-date
phpmyadmin-prod is up-to-date
Creating app-prod ... done

补充说明 #

• 如果必须保留自定义容器名，可使用docker-compose up -d --force-recreate强制重建，但这会导致容器重启，临时数据丢失，不推荐在生产环境使用。
• depends_on仅控制容器启动顺序，不保证服务完全就绪（比如MySQL启动完成），如果需要等待服务就绪后再启动app，建议添加健康检查或启动脚本。

内容的提问来源于stack exchange，提问作者Mohamed Alaa