logo标签列表

如何在Docker Hub上使用特定架构构建Docker镜像？

dockerdockerfiledockerhub
9

我在Docker Hub上有这些自动化构建:

docker hub automated builds

以下是两个Dockerfile的参考：

以下是arm32v7构建的日志:

Building in Docker Cloud's infrastructure...
Cloning into '.'...
Warning: Permanently added the RSA host key for IP address '192.30.253.113' to the list of known hosts.
Reset branch 'master'
Your branch is up-to-date with 'origin/master'.
Executing build hook...
Sending build context to Docker daemon 88.06kB
Step 1/17 : ARG ALPINE_VERSION="3.8"
Step 2/17 : ARG S6_OVERLAY_VERSION="1.21.7.0"
Step 3/17 : FROM golang:1.11-alpine${ALPINE_VERSION} AS builder
1.11-alpine3.8: Pulling from library/golang
169185f82c45: Pulling fs layer
34c29055ee42: Pulling fs layer
29802c64cdfc: Pulling fs layer
dd82873a5b09: Pulling fs layer
b711937b138a: Pulling fs layer
dd82873a5b09: Waiting
b711937b138a: Waiting
29802c64cdfc: Verifying Checksum
29802c64cdfc: Download complete
34c29055ee42: Verifying Checksum
34c29055ee42: Download complete
b711937b138a: Verifying Checksum
b711937b138a: Download complete
169185f82c45: Verifying Checksum
169185f82c45: Download complete
169185f82c45: Pull complete
34c29055ee42: Pull complete
29802c64cdfc: Pull complete
dd82873a5b09: Verifying Checksum
dd82873a5b09: Download complete
dd82873a5b09: Pull complete
b711937b138a: Pull complete
Digest: sha256:9657ef82d7ead12e0c88c7f4708e78b50c5fd3c1893ac0f2f0924ab98873aad8
Status: Downloaded newer image for golang:1.11-alpine3.8
---> be1230a1b343
Step 4/17 : RUN apk update && apk add --no-cache --virtual build-dependencies git && go get -u github.com/nmrshll/gphotos-uploader-cli/cmd/gphotos-uploader-cli && cd /go/src/github.com/nmrshll && rm -rf gphotos-uploader-cli && git clone https://github.com/rfgamaral/gphotos-uploader-cli.git --branch docker && rm -rf oauth2-noserver && git clone https://github.com/rfgamaral/oauth2-noserver.git --branch docker && cd gphotos-uploader-cli/cmd/gphotos-uploader-cli && GOOS=linux GOARCH=amd64 go build -ldflags='-w -s' -o /go/bin/gphotos-uploader-cli && apk del build-dependencies
---> Running in 79c1d68ad8b0
fetch http://dl-cdn.alpinelinux.org/alpine/v3.8/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.8/community/x86_64/APKINDEX.tar.gz
v3.8.2-53-g53558ad6fc [http://dl-cdn.alpinelinux.org/alpine/v3.8/main]
v3.8.2-53-g53558ad6fc [http://dl-cdn.alpinelinux.org/alpine/v3.8/community]
OK: 9544 distinct packages available
fetch http://dl-cdn.alpinelinux.org/alpine/v3.8/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.8/community/x86_64/APKINDEX.tar.gz
(1/7) Installing nghttp2-libs (1.32.0-r0)
(2/7) Installing libssh2 (1.8.0-r3)
(3/7) Installing libcurl (7.61.1-r1)
(4/7) Installing expat (2.2.5-r0)
(5/7) Installing pcre2 (10.31-r0)
(6/7) Installing git (2.18.1-r0)
(7/7) Installing build-dependencies (0)
Executing busybox-1.28.4-r3.trigger
OK: 19 MiB in 21 packages
Cloning into 'gphotos-uploader-cli'...
Cloning into 'oauth2-noserver'...
(1/7) Purging build-dependencies (0)
(2/7) Purging git (2.18.1-r0)
(3/7) Purging libcurl (7.61.1-r1)
(4/7) Purging nghttp2-libs (1.32.0-r0)
(5/7) Purging libssh2 (1.8.0-r3)
(6/7) Purging expat (2.2.5-r0)
(7/7) Purging pcre2 (10.31-r0)
Executing busybox-1.28.4-r3.trigger
OK: 5 MiB in 14 packages
Removing intermediate container 79c1d68ad8b0
---> 17b221a9ee49
Step 5/17 : FROM amd64/alpine:${ALPINE_VERSION}
3.8: Pulling from amd64/alpine
169185f82c45: Already exists
Digest: sha256:616d0d0ff1583933ed10a7b3b4492899942016c0577d43a1c506c0aad8ab4da8
Status: Downloaded newer image for amd64/alpine:3.8
---> 491e0ff7a8d5
Step 6/17 : LABEL maintainer="master@ricardoamaral.net"
---> Running in e58b7fcdb220
Removing intermediate container e58b7fcdb220
---> c525e340a42d
Step 7/17 : ARG BUILD_DATE
---> Running in 0a9417e1adcd
Removing intermediate container 0a9417e1adcd
---> 9f6c69125803
Step 8/17 : ARG S6_OVERLAY_VERSION
---> Running in 93a8cd6996b9
Removing intermediate container 93a8cd6996b9
---> 6034d93430da
Step 9/17 : ARG VCS_REF
---> Running in 8f6fc7d81c71
Removing intermediate container 8f6fc7d81c71
---> 74180d38dbc0
Step 10/17 : LABEL org.label-schema.build-date="${BUILD_DATE}" org.label-schema.description="Mass upload media folders to your Google Photos account with this Docker image." org.label-schema.name="rfgamaral/gphotos-uploader" org.label-schema.schema-version="1.0" org.label-schema.vcs-ref="${VCS_REF}" org.label-schema.vcs-url="https://github.com/rfgamaral/docker-gphotos-uploader.git"
---> Running in 08cf19c6f46a
Removing intermediate container 08cf19c6f46a
---> 106104e2ef17
Step 11/17 : ENV GPU_SCHEDULE="0 */8 * * *"
---> Running in edea63c892b9
Removing intermediate container edea63c892b9
---> d69ae92742d2
Step 12/17 : ADD https://github.com/just-containers/s6-overlay/releases/download/v${S6_OVERLAY_VERSION}/s6-overlay-amd64.tar.gz /tmp/
---> a7448cda217f
Step 13/17 : RUN apk update && apk add --no-cache curl && tar xzf /tmp/s6-overlay-amd64.tar.gz -C / && rm -rf /tmp/*
---> Running in 5d9ee7e3941d
fetch http://dl-cdn.alpinelinux.org/alpine/v3.8/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.8/community/x86_64/APKINDEX.tar.gz
v3.8.2-53-g53558ad6fc [http://dl-cdn.alpinelinux.org/alpine/v3.8/main]
v3.8.2-53-g53558ad6fc [http://dl-cdn.alpinelinux.org/alpine/v3.8/community]
OK: 9544 distinct packages available
fetch http://dl-cdn.alpinelinux.org/alpine/v3.8/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.8/community/x86_64/APKINDEX.tar.gz
(1/5) Installing ca-certificates (20171114-r3)
(2/5) Installing nghttp2-libs (1.32.0-r0)
(3/5) Installing libssh2 (1.8.0-r3)
(4/5) Installing libcurl (7.61.1-r1)
(5/5) Installing curl (7.61.1-r1)
Executing busybox-1.28.4-r3.trigger
Executing ca-certificates-20171114-r3.trigger
OK: 6 MiB in 18 packages
Removing intermediate container 5d9ee7e3941d
---> 14fc569893de
Step 14/17 : COPY --from=builder /go/bin/gphotos-uploader-cli /usr/local/bin/gphotos-uploader-cli
---> 32fa657de51c
Step 15/17 : COPY rootfs/ /
---> 1639f6e639b4
Step 16/17 : VOLUME ["/config", "/photos"]
---> Running in 440d1d13cd60
Removing intermediate container 440d1d13cd60
---> fd730f9c1ebb
Step 17/17 : ENTRYPOINT ["/init"]
---> Running in 197c889006b2
Removing intermediate container 197c889006b2
---> 4e66fc7b481d
Successfully built 4e66fc7b481d
Successfully tagged rfgamaral/gphotos-uploader:latest-arm32v7
Pushing index.docker.io/rfgamaral/gphotos-uploader:latest-arm32v7...
Done!
Build finished

正如您所看到的，日志只引用amd64而不是在Dockerfile.arm32v7文件中明显存在的arm32v7或armhf。为什么Docker Hub会更改以下内容：
  • arm32v7/alpine:${ALPINE_VERSION} 更改为 amd64/alpine:${ALPINE_VERSION}
  • s6-overlay-armhf.tar.gz 更改为 s6-overlay-amd64.tar.gz
  • GOARCH=arm GOARM=7 更改为 GOARCH=amd64
这就像它正在使用Dockerfile而不是Dockerfile.arm32v7，但是a）这不是我在自动构建配置中选择的“Dockerfile位置”，b）Docker Hub构建部分作为“Dockerfile”选项卡显示用于构建的Dockerfile并且它显示正确的Dockerfile。
这是Docker Hub上的错误还是我的问题？
1
Dockerfile.arm32v7文件无法访问。这会影响其他观看者的问题。 - EduMelo
3个回答
19

经过一点研究，我解决了自己的问题...首先，我犯了一个愚蠢的错误，其次，我忘记了非常重要的事情。以下是我如何解决我的问题：

愚蠢的错误

尽管我为每个自动构建指定了不同的Dockerfile，但我也有一个build钩子，它正在覆盖docker build命令，并且它默认选择所有构建的Dockerfile而不是选择正确的文件。

修改build钩子文件：

#!/bin/bash

docker build \
    --file "${DOCKERFILE_PATH}" \
    --build-arg BUILD_DATE="$(date -u +"%Y-%m-%dT%H:%M:%SZ")" \
    --build-arg VCS_REF="$(git rev-parse --short HEAD)" \
    --tag "$IMAGE_NAME" \
    .

重要的事情

就像@JanGaraj在他的答案中提到的那样，Docker Hub在amd64上运行，因此无法运行其他体系结构的二进制文件。如何使用Docker Hub自动化构建构建多架构镜像？借助qemu-user-static和更多的勾子。我在这个GitHub问题上找到了答案，但是我将在这里发布我特定用例的完整答案：

我的示例项目树:

.
├── Dockerfile
├── Dockerfile.aarch64
├── Dockerfile.armhf
└── hooks
    ├── build
    ├── post_checkout
    └── pre_build

post_checkout 钩子文件：

#!/bin/bash

BUILD_ARCH=$(echo "${DOCKERFILE_PATH}" | cut -d '.' -f 2)

[ "${BUILD_ARCH}" == "Dockerfile" ] && \
    { echo 'qemu-user-static: Download not required for current arch'; exit 0; }

QEMU_USER_STATIC_ARCH=$([ "${BUILD_ARCH}" == "armhf" ] && echo "${BUILD_ARCH::-2}" || echo "${BUILD_ARCH}")
QEMU_USER_STATIC_DOWNLOAD_URL="https://github.com/multiarch/qemu-user-static/releases/download"
QEMU_USER_STATIC_LATEST_TAG=$(curl -s https://api.github.com/repos/multiarch/qemu-user-static/tags \
    | grep 'name.*v[0-9]' \
    | head -n 1 \
    | cut -d '"' -f 4)

curl -SL "${QEMU_USER_STATIC_DOWNLOAD_URL}/${QEMU_USER_STATIC_LATEST_TAG}/x86_64_qemu-${QEMU_USER_STATIC_ARCH}-static.tar.gz" \
    | tar xzv

pre_build 钩子文件：

#!/bin/bash

BUILD_ARCH=$(echo "${DOCKERFILE_PATH}" | cut -d '.' -f 2)

[ "${BUILD_ARCH}" == "Dockerfile" ] && \
    { echo 'qemu-user-static: Registration not required for current arch'; exit 0; }

docker run --rm --privileged multiarch/qemu-user-static:register --reset

Dockerfile 文件:

FROM amd64/alpine:3.8
(...)

Dockerfile.aarch64文件：

FROM arm64v8/alpine:3.8
COPY qemu-aarch64-static /usr/bin/
(...)

Dockerfile.armhf 文件：

FROM arm32v6/alpine:3.8
COPY qemu-arm-static /usr/bin/
(...)

就是这样！

我基本上按照你的步骤来构建我的 .NET CORE 应用程序运行在 ARM32 架构下，但还是失败了。我的 Dockerfile.armhf 如下所示：FROM mcr.microsoft.com/dotnet/core/aspnet:3.1.7-buster-slim-arm32v7 AS base COPY qemu-arm-static /usr/bin/。从 Docker Hub 的构建日志中，我可以看到 COPY qemu-arm-static /usr/bin/ 已经成功了。但最后总是出现 [91mstandard_init_linux.go:211: exec user process caused "no such file or directory" 和 [0mThe command '/bin/sh -c dotnet restore "MyAppMain/Main.csproj"' returned a non-zero code: 1 build hook failed! (1)。 - Shawn
在 FROM 指令中添加架构前缀，这正是我所缺失的，而且我并没有意识到这是可能的。谢谢！ - Gio
4
现在你也可以使用docker buildx为不同的架构构建，而不必为每个架构维护单独的Dockerfile。使用Buildx构建多架构Docker镜像介绍了其工作原理。 基本上，你需要：
  1. 在主机上使用fix-binary标志在binfmt_misc中注册你的QEMU模拟器，以便它可以在容器中运行而无需将其复制到容器文件系统中
  2. 使用docker buildx build --platform linux/arm/v7 ...指示构建器为与构建主机不同的架构进行构建
小心不要被 buildx 的安全感所迷惑。安装依赖项时，如果期望一种架构，然后尝试在另一种架构上运行它们，可能会导致严重的运行时错误。 - Gio
3

Docker镜像golang:1.11-alpine3.8是多架构镜像。可用架构列表：

$ docker run --rm mplatform/mquery golang:1.11-alpine3.8
Image: golang:1.11-alpine3.8
 * Manifest List: Yes
 * Supported platforms:
   - linux/amd64
   - linux/arm/v6
   - linux/arm64
   - linux/386
   - linux/ppc64le
   - linux/s390x

首先的问题是：此Docker镜像不支持平台arm32/v7。第二个问题是：Docker守护程序将拉取与其相同平台的平台镜像。我猜Docker Hub运行在amd64上，所以它会选择amd64。
我的建议是：构建静态链接二进制文件+跨平台Go编译（GOARCH=arm GOARM=7）+使用SCRATCH基础镜像，这样您就可以创建arm7和amd64 Docker了。
如果我没有错的话，我正是在做你提出的事情，唯一的区别是我使用 alpine 而不是 scratch 并且我选择了适当的 alpine 平台。此外，这并不能真正解释为什么构建会将 GOARCH=arm 更改为 GOARCH=amd64。一个是根据它运行的系统选择适当的平台，另一个是实际上更改我的 Dockerfile 的内容。那没有任何意义。 - rfgamaral
你说得对。也许 arm32v7/alpine:3.8 是一些特殊的镜像。我无法将其拉到我的本地机器上，因为它不可用。也许 Docker Hub 已经选择了一些等效的镜像（即 amd64）。 - Jan Garaj
尝试使用arm32v6/alpine:3.8（可用）代替arm32v7/alpine:3.8来证明这个理论。我猜它会失败，因为Docker Hub无法在amd63平台上运行arm32二进制文件。 - Jan Garaj
你说得对，但那不是我唯一的问题。请查看我的回答，了解我如何解决我的问题。谢谢你的帮助 :) - rfgamaral
网页内容由stack overflow 提供, 点击上面的
可以查看英文原文，
原文链接