“##[error] 来自守护程序的错误响应：无法在 Dockerfile 中达到构建目标 <stage>”仅在 CI 管道期间

Question

我在 PR 管道中遇到此错误，我不确定原因和解决方案。

Docker 任务模板化得很好，阶段确实存在于我的 Dockerfile:

# docker.yaml
parameters:
- name: service
  default: ''
- name: jobName
  default: ''
- name: jobDisplayName
  default: ''
- name: taskDisplayName
  default: ''
- name: dockerCommand
  default: ''
- name: target
  default: ''
- name: tag
  default: ''

jobs:
- job: ${{ parameters.jobName }}
  displayName: ${{ parameters.jobDisplayName }}
  # Handle whether to run service or not
  variables:
    servicesChanged: $[ stageDependencies.Changed.Changes.outputs['detectChanges.servicesChanged'] ]
  condition: or(contains(variables['servicesChanged'], '${{ parameters.service }}'), eq(variables['Build.Reason'], 'Manual'))
  steps: 
  # Set to app repo
  - checkout: app
  # Run the Docker task
  - task: Docker@2
    # Run if there have been changes
    displayName: ${{ parameters.taskDisplayName }}
    inputs:
      command: ${{ parameters.dockerCommand }}
      repository: $(imageRepository)-${{ parameters.service }}
      dockerfile: $(dockerFilePath)/${{ parameters.service }}/docker/Dockerfile
      buildContext: $(dockerFilePath)/${{ parameters.service }}
      containerRegistry: $(dockerRegistryServiceConnection)
      arguments: --target ${{ parameters.target }}
      tags: |
        ${{ parameters.tag }}-$(Build.BuildNumber)

# Dockerfile
# syntax=docker/dockerfile:1
# creating a python base with shared environment variables
FROM python:3.8-slim as python-base
ENV PYTHONUNBUFFERED=1 \
    PYTHONDONTWRITEBYTECODE=1 \
    PIP_NO_CACHE_DIR=off \
    PIP_DISABLE_PIP_VERSION_CHECK=on \
    PIP_DEFAULT_TIMEOUT=100 \
    POETRY_HOME="/opt/poetry" \
    POETRY_VIRTUALENVS_IN_PROJECT=true \
    POETRY_NO_INTERACTION=1 \
    PYSETUP_PATH="/opt/pysetup" \
    VENV_PATH="/opt/pysetup/.venv"
ENV PATH="$POETRY_HOME/bin:$VENV_PATH/bin:$PATH"


# builder-base is used to build dependencies
FROM python-base as builder-base
RUN apt-get update \
    && apt-get install --no-install-recommends -y \
        curl \
        build-essential

# Install Poetry - respects $POETRY_VERSION & $POETRY_HOME
ENV POETRY_VERSION=1.1.8
RUN curl -sSL https://raw.githubusercontent.com/sdispater/poetry/master/get-poetry.py | python

# We copy our Python requirements here to cache them
# and install only runtime deps using poetry
WORKDIR $PYSETUP_PATH
COPY ./poetry.lock ./pyproject.toml ./
RUN poetry install --no-dev


# 'development' stage installs all dev deps and can be used to develop code.
# For example using docker-compose to mount local volume under /app
FROM python-base as development

# Copying poetry and venv into image
COPY --from=builder-base $POETRY_HOME $POETRY_HOME
COPY --from=builder-base $PYSETUP_PATH $PYSETUP_PATH

# Copying in our entrypoint
# COPY ./docker/docker-entrypoint.sh /docker-entrypoint.sh
RUN chmod +x . /opt/pysetup/.venv/bin/activate

# venv already has runtime deps installed we get a quicker install
WORKDIR $PYSETUP_PATH
RUN poetry install
WORKDIR /app
COPY . .
EXPOSE 5000
CMD [ "python", "src/manage.py", "runserver", "0.0.0.0:5000"]


# 'unit-tests' stage runs our unit tests with unittest and coverage.  
FROM development AS unit-tests
RUN coverage run --omit='src/manage.py,src/config/*,*/.venv/*,*/*__init__.py,*/tests.py,*/admin.py' src/manage.py test src --tag=ut && \
    coverage report

Dockerfile 被正确找到并且管道看起来它开始构建图像，但随后抛出此错误。我可以在本地运行 a docker build ... --target unit-tests 没有问题，所以它与 Azure Pipelines 隔离。

关于可能导致此问题的建议？

编辑：这是项目结构：

app/
  admin/
    docker/
      Dockerfile
      entrypoint.sh
    src/
      ...
  api/
    docker/
      Dockerfile
      entrypoint.sh
    src/
      ...
  portal/
    docker/
      Dockerfile
      entrypoint.sh
    src/
      ...

这是 devspace.yaml 的一部分：

admin-ut:
  image: ${APP-NAME}/${ADMIN-UT}
  dockerfile: ${ADMIN}/docker/Dockerfile
  context: ${ADMIN}/
  build:
    buildKit:
      args: []
      options:
        target: unit-tests

编辑 2：

这个问题可能与没有 BuildKit 这个问题有关：

Azure Pipelines: Build a specific stage in a multistage Dockerfile without building non-dependent stages

但是有 Github 个相关问题：

https://github.com/MicrosoftDocs/azure-devops-docs/issues/9196#issuecomment-761624398

所以我将 Azure Pipelines 的 docker.yaml 修改为：

  - task: Docker@2
    # Run if there have been changes
    displayName: ${{ parameters.taskDisplayName }}
    inputs:
      command: ${{ parameters.dockerCommand }}
      repository: $(imageRepository)-${{ parameters.service }}
      dockerfile: $(dockerFilePath)/${{ parameters.service }}/docker/Dockerfile
      buildContext: $(dockerFilePath)/${{ parameters.service }}
      containerRegistry: $(dockerRegistryServiceConnection)
      arguments: --target ${{ parameters.target }}
      tags: |
        ${{ parameters.tag }}-$(Build.BuildNumber)
    env:
      DOCKER_BUILDKIT: 1

现在我得到了更详细的错误输出：

failed to solve with frontend dockerfile.v0: failed to create LLB definition: target stage unit-tests could not be found
##[error]#1 [internal] load build definition from Dockerfile
##[error]#1 sha256:acc1b908d881e469d44e7f005ceae0820d5ee08ada351a0aa2a7b8e749c8f6fe
##[error]#1 transferring dockerfile: 974B done
##[error]#1 DONE 0.0s
##[error]#2 [internal] load .dockerignore
##[error]#2 sha256:189c0a02bba84ed5c5f9ea82593d0e664746767c105d65afdf3cd0771eeb378e
##[error]#2 transferring context: 346B done
##[error]#2 DONE 0.0s
##[error]failed to solve with frontend dockerfile.v0: failed to create LLB definition: target stage unit-tests could not be found
##[error]The process '/usr/bin/docker' failed with exit code 1

Answer 1

好的，我想我现在已经解决了，管道阶段运行成功了。这是添加 DOCKER_BUILDKIT: 1 的组合，例如：

  - task: Docker@2
    # Run if there have been changes
    displayName: ${{ parameters.taskDisplayName }}
    inputs:
      command: ${{ parameters.dockerCommand }}
      repository: $(imageRepository)-${{ parameters.service }}
      dockerfile: $(dockerFilePath)/${{ parameters.service }}/docker/Dockerfile
      buildContext: $(dockerFilePath)/${{ parameters.service }}
      containerRegistry: $(dockerRegistryServiceConnection)
      arguments: --target ${{ parameters.target }}
      tags: |
        ${{ parameters.tag }}-$(Build.BuildNumber)
    env:
      DOCKER_BUILDKIT: 1

然后从每个 Dockerfile 中删除 # syntax=docker/dockerfile:1。对 Dockerfile 进行修改后，本地环境仍然有效。

Answer 2

几分钟前我遇到了同样的错误。之前我的客服是这样的：

services:
  client:     
    container_name: client
    image: client
    build: ./client
    ports:
     - '3000:3000'
   volumes:
     - ./client:/app
     - ./app/node_modules

我在服务开始时移动了 build: ./client，它对我有用。

之后是这样的：

services:
  client:     
    build: ./client
    container_name: client
    image: client
    ports:
     - '3000:3000'
   volumes:
     - ./client:/app
     - ./app/node_modules

“##[error] 来自守护程序的错误响应：无法在 Dockerfile 中达到构建目标 <stage>”仅在 CI 管道期间

"##[error]Error response from daemon: failed to reach build target <stage> in Dockerfile" only during CI pipeline

docker

azure-devops

azure-pipelines

azure-pipelines-yaml

azure-pipelines-tasks