Azure DevOps使用DockerCompose推送镜像到DockerHub标签与推送失败求助

修改后的完整pipeline配置 #

trigger:
  - development

resources:
  - repo: self

variables:
  dockerhubNS: 'myDockerHub'
  ImageName: 'myDockerImageName'
  ImageTag: 'demo_all'
  fullImageName: '$(dockerhubNS)/$(ImageName):$(ImageTag)'

stages:
  - stage: Build
    displayName: Build and push image
    jobs:
      - job: Build
        displayName: Build push
        pool:
          vmImage: ubuntu-latest
        steps:
          - task: DockerCompose@0
            displayName: Build node service image
            inputs:
              containerregistrytype: 'Container Registry'
              dockerRegistryEndpoint: 'portal_demo'
              dockerComposeFile: '$(Build.SourcesDirectory)/docker-compose.yml'
              action: 'Build services'
              serviceName: 'node'
              includeSourceTags: false
              includeLatestTag: false
              additionalImageTags: '$(ImageTag)'
          # 显式打标签步骤，避免镜像名匹配偏差
          - script: |
              docker tag $(dockerhubNS)/$(ImageName):$(ImageTag) $(fullImageName)
            displayName: Tag image explicitly
          - task: DockerCompose@0
            displayName: Push image to DockerHub
            inputs:
              containerregistrytype: 'Container Registry'
              dockerRegistryEndpoint: 'portal_demo'
              dockerComposeFile: '$(Build.SourcesDirectory)/docker-compose.yml'
              action: 'Push services'
              serviceName: 'node'
              includeSourceTags: false
              includeLatestTag: true
              additionalImageTags: '$(ImageTag)'

改动说明&问题解决逻辑 #

• 原构建步骤使用自定义Run a Docker Compose command动作，该场景下任务自带的标签、镜像名前缀参数不会生效，导致构建出来的镜像标签不符合预期，直接改成Build services动作并指定serviceName为node即可激活所有标签配置，解决标签不生效的问题。
• 新增了显式打标签的脚本步骤，确保本地镜像存在完全匹配myDockerHub/myDockerImageName:demo_all格式的版本，推送步骤和构建步骤使用完全一致的标签规则，避免推送时去匹配带hub.docker.com前缀的不存在的镜像，解决推送找不到本地镜像的问题。
• 移除了冗余的qualifyImageNames配置，避免任务自动给镜像名加registry前缀导致和DockerHub的命名规则冲突。

额外注意：你在Azure DevOps中配置的portal_demo服务连接，关联的DockerHub账号必须要有$(dockerhubNS)命名空间下的镜像推送权限，否则标签正确也会出现推送权限报错。

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