Google Cloud Build 使用 Dockerfile 上的卷答案

【问题标题】：Google Cloud Build using volumes on DockerfileGoogle Cloud Build 使用 Dockerfile 上的卷
【发布时间】：2021-01-20 14:55:02
【问题描述】：

我正在尝试为我的应用程序构建构建管道并使用卷在步骤之间共享特定文件夹。

问题是因为在我的第一步 (unit-tests) 我必须在 requirements.txt 上安装所有库才能运行我的单元测试。之后，我必须在其他步骤中构建运行 Dockerfile 的应用程序。我不想再次重新安装所有要求，所以，我想复制已经安装的要求并将它们粘贴到 docker build 步骤中。我能做到吗？我关注了这个帖子并试图复制到我的现实中，但我仍然遇到问题。

Passing files from Google Cloud Container Builder to Docker build task

这是我所做的一个示例：

我的 cloudbuild.yaml：

- id: unit-tests
  name: python:3-alpine
  entrypoint: sh
  dir: my-dir
  args:
    - -c
    - |
      apk add --virtual build_dependencies build-base
      apk add --no-cache libstdc++
      pip install --no-cache-dir -r requirements.txt
      apk del build_dependencies
      python -m unittest discover --verbose
      cp -Rv /usr/local/lib/python3.8/site-packages/* /requirements
  volumes:
    - name: 'requirements'
      path: /requirements

- id: docker-build
  name: gcr.io/cloud-builders/docker
  dir: my-dir
  args:
  - build
  - --tag=gcr.io/${PROJECT_ID}/eta:test
  - '.'
  volumes:
    - name: 'requirements'
      path: /requirements
  waitFor: ['unit-tests']

images:
- 'gcr.io/$PROJECT_ID/eta:test'

timeout: 3600s

这是我的 Dockerfile：

from python:3-alpine

RUN set -eux; \
    apk add --virtual build_dependencies build-base; \
    apk add --no-cache libstdc++; \
    apk del build_dependencies; 

COPY /requirements/* /usr/local/lib/python3.8/site-packages/
COPY . /app
RUN ["chmod", "+x", "/app/entry.sh"]
WORKDIR /app
ENTRYPOINT [ "/app/entry.sh" ]

我在 dockerfile 中找不到 /requirements 文件夹，这是错误消息：

Step #1 - "docker-build": Step 3/7 : COPY /requirements/* /usr/local/lib/python3.8/site-packages/
Step #1 - "docker-build": COPY failed: no source files were specified
Finished Step #1 - "docker-build"
ERROR
ERROR: build step 1 "gcr.io/cloud-builders/docker" failed: step exited with non-zero status: 1

我不确定我的做法是否正确。

【问题讨论】：

你正在尝试的应该会成功。您可以尝试添加一个中间步骤，该步骤将列出 /requirements 的内容，以确认上一步成功。我会尝试重现。注意您也可以在根目录添加options 并在那里定义卷，它们将应用于所有步骤。

标签： python-3.x docker build google-cloud-build

【解决方案1】：

Cloud Build (VM) 在各个步骤中持续存在 /workspace，因此您可以创建例如/workspace/requirements 并在后续步骤中使用 requirements。

PROJECT=[[YOUR-PROJECT]]
BILLING=[[YOUR-BILLING]]

gcloud projects create ${PROJECT}

gcloud beta billing projects link ${PROJECT} \
--billing-account=${BILLING}

gcloud services enable cloudbuild.googleapis.com \
--project=${PROJECT}

然后：

steps:

  - id: also
    name: busybox
    entrypoint: sh
    dir: x
    args:
      - -c
      - |
        mkdir -p /workspace/requirements
        echo "Hello Freddie" > /workspace/requirements/freddie.txt

  - id: after
    name: gcr.io/cloud-builders/docker
    args:
      - build
      - --tag=gcr.io/${PROJECT_ID}/test
      - .
images:
  - gcr.io/${PROJECT_ID}/test

还有Dockerfile:

FROM busybox

WORKDIR /test

COPY /requirements/* .

RUN ls -la

ENTRYPOINT ["more","/test/freddie.txt"]

还有：

gcloud builds submit . \
--config=./cloudbuild.yaml \
--project=${PROJECT}

产量：

BUILD
Starting Step #0 - "also"
Step #0 - "also": Pulling image: busybox
Step #0 - "also": Using default tag: latest
Step #0 - "also": latest: Pulling from library/busybox
Step #0 - "also": Digest: sha256:2ca5e69e
Step #0 - "also": Status: Downloaded newer image for busybox:latest
Step #0 - "also": docker.io/library/busybox:latest
Finished Step #0 - "also"
Starting Step #1 - "after"
Step #1 - "after": Already have image (with digest): gcr.io/cloud-builders/docker
Step #1 - "after": Sending build context to Docker daemon   7.68kB
Step #1 - "after": Step 1/5 : FROM busybox
Step #1 - "after":  ---> 6858809bf669
Step #1 - "after": Step 2/5 : WORKDIR /test
Step #1 - "after":  ---> Running in 7e075adce9eb
Step #1 - "after": Removing intermediate container 7e075adce9eb
Step #1 - "after":  ---> 78f7b2faec16
Step #1 - "after": Step 3/5 : COPY /requirements/* .
Step #1 - "after":  ---> 1ec6a35c1deb
Step #1 - "after": Step 4/5 : RUN ls -la
Step #1 - "after":  ---> Running in 943ddad6434c
Step #1 - "after": total 12
Step #1 - "after": .
Step #1 - "after": ..
Step #1 - "after": freddie.txt
Step #1 - "after": Removing intermediate container 943ddad6434c
Step #1 - "after":  ---> 634072b8aec4
Step #1 - "after": Step 5/5 : ENTRYPOINT ["more","/test/freddie.txt"]
Step #1 - "after":  ---> Running in 13c43b5ca924
Step #1 - "after": Removing intermediate container 13c43b5ca924
Step #1 - "after":  ---> f0ebfe1e8e33
Step #1 - "after": Successfully built f0ebfe1e8e33
Step #1 - "after": Successfully tagged gcr.io/.../test:latest
Finished Step #1 - "after"
PUSH

使用volumes 的问题是这些不会在 docker build 的上下文中。因此，如果您更喜欢使用卷，则需要将卷的内容复制到 /workspace。

然后，当您运行gcr.io/cloud-builders/docker 步骤时，/workspace 被挂载为根，因此您可以以/requirements 的身份访问/workspace/requirements：

然后：

steps:
  - id: before
    name: busybox
    entrypoint: sh
    dir: x
    args:
      - -c
      - |
        echo "Hello Freddie" > /requirements/freddie.txt
    volumes:
      - name: requirements
        path: /requirements

  - id: during
    name: busybox
    entrypoint: sh
    dir: x
    args:
      - -c
      - |
        more /requirements/freddie.txt
    volumes:
      - name: requirements
        path: /requirements

  - id: fix
    name: busybox
    entrypoint: sh
    args:
      - -c
      - |
        ls -la /workspace
        ls -la /requirements
        mkdir -p /workspace/requirements
        cp -r /requirements /workspace/requirements
        ls -la /workspace/requirements
    volumes:
      - name: requirements
        path: /requirements

  - id: after
    name: gcr.io/cloud-builders/docker
    args:
      - build
      - --tag=gcr.io/${PROJECT_ID}/test
      - .

images:
  - gcr.io/${PROJECT_ID}/test

产量：

BUILD
Starting Step #0 - "before"
Step #0 - "before": Pulling image: busybox
Step #0 - "before": Using default tag: latest
Step #0 - "before": latest: Pulling from library/busybox
Step #0 - "before": Digest: sha256:2ca5e69e
Step #0 - "before": Status: Downloaded newer image for busybox:latest
Step #0 - "before": docker.io/library/busybox:latest
Finished Step #0 - "before"
Starting Step #1 - "during"
Step #1 - "during": Already have image: busybox
Step #1 - "during": Hello Freddie
Finished Step #1 - "during"
Starting Step #2 - "fix"
Step #2 - "fix": Already have image: busybox
Step #2 - "fix": total 24
Step #2 - "fix": .
Step #2 - "fix": ..
Step #2 - "fix": Dockerfile
Step #2 - "fix": cloudbuild.yaml
Step #2 - "fix": requirements
Finished Step #2 - "fix"
Starting Step #3 - "after"
Step #3 - "after": Already have image (with digest): gcr.io/cloud-builders/docker
Step #3 - "after": Sending build context to Docker daemon  8.192kB
Step #3 - "after": Step 1/5 : FROM busybox
Step #3 - "after":  ---> 6858809bf669
Step #3 - "after": Step 2/5 : WORKDIR /test
Step #3 - "after":  ---> Running in 236aa78f2229
Step #3 - "after": Removing intermediate container 236aa78f2229
Step #3 - "after":  ---> cf05164e8175
Step #3 - "after": Step 3/5 : COPY /requirements/* .
Step #3 - "after":  ---> f5dee710b4d7
Step #3 - "after": Step 4/5 : RUN ls -la
Step #3 - "after":  ---> Running in 8a30309a1536
Step #3 - "after": total 12
Step #3 - "after": .
Step #3 - "after": ..
Step #3 - "after": freddie.txt
Step #3 - "after": Removing intermediate container 8a30309a1536
Step #3 - "after":  ---> 20e2e99c3818
Step #3 - "after": Step 5/5 : ENTRYPOINT ["more","/test/freddie.txt"]
Step #3 - "after":  ---> Running in cc6a57aaa103
Step #3 - "after": Removing intermediate container cc6a57aaa103
Step #3 - "after":  ---> 0a50096e471c
Step #3 - "after": Successfully built 0a50096e471c
Step #3 - "after": Successfully tagged gcr.io/.../test:latest
Finished Step #3 - "after"
PUSH
Pushing gcr.io/.../test
...
DONE

【讨论】：

感谢您的回复！我决定像您在第一个示例中所说的那样在没有音量的情况下制作它并且第一次没有工作，但我注意到问题出在我的 dir 我正在像您创建的那样创建工作区文件夹/worspace/requirements 并且在我的 docker-build 步骤中，我正在执行 my-dir/ 目录上的命令。所以，我必须创建 /workspace/my-dir/requirements ，它就像一个魅力！非常感谢！
超级！我很高兴听到它有帮助