如何将docker构建的架构设置为arm64?

问题描述 投票:0回答:6

我有一个在 amd64 上运行的 Dockerfile,但想在 arm64 上运行。由于 go build 工具采用 GOARCH=arm64 作为参数,因此我不需要任何其他交叉编译工具来制作二进制文件。

# Run the build
FROM mojlighetsministeriet/go-polymer-faster-build
ENV WORKDIR /go/src/github.com/mojlighetsministeriet/email
COPY . $WORKDIR
WORKDIR $WORKDIR
RUN go get -t -v ./...
RUN CGO_ENABLED=0 GOOS=linux GOARCH=arm64 go build

# Create the final docker image
FROM scratch
COPY --from=0 /etc/ssl/certs/ca-certificates.crt /etc/ssl/certs/ca-certificates.crt
COPY --from=0 /go/src/github.com/mojlighetsministeriet/email/email /
ENTRYPOINT ["/email"]

问题是生成的图像被标记为错误的架构 amd64 而不是 arm64。如何将参数传递给 docker build 以便将 Architecture 设置为 arm64?

$ docker image inspect mojlighetsministeriet/email-arm64                            
[
    {
        "Id": "sha256:33bcd7da8631c7a0829d61cc53479a26ab7f31fab1cb039105de415ddc6178f3",
        "RepoTags": [
            "mojlighetsministeriet/email-arm64:latest"
        ],
        "RepoDigests": [
            "mojlighetsministeriet/email-arm64@sha256:ab3f05d5597c3a304953b5c14f795179aa75bdfd458af3dc3cfb8b8d8eb87bc3"
        ],
        "Parent": "sha256:e5888262d93ea0946b5fd8146cf1c19ec3a7bac4d36eb51848ef0aefa75cf8e7",
        "Comment": "",
        "Created": "2017-12-05T18:36:36.273648787Z",
        "Container": "7a226edb3b52aaeeefec9e0fb4dd1da50d84992fb6cc374aeda9d82eec1bb2c8",
        "ContainerConfig": {
            "Hostname": "7a226edb3b52",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": [
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
            ],
            "Cmd": [
                "/bin/sh",
                "-c",
                "#(nop) ",
                "ENTRYPOINT [\"/email\"]"
            ],
            "Image": "sha256:e5888262d93ea0946b5fd8146cf1c19ec3a7bac4d36eb51848ef0aefa75cf8e7",
            "Volumes": null,
            "WorkingDir": "",
            "Entrypoint": [
                "/email"
            ],
            "OnBuild": null,
            "Labels": {}
        },
        "DockerVersion": "17.10.0-ce",
        "Author": "",
        "Config": {
            "Hostname": "",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": [
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
            ],
            "Cmd": null,
            "Image": "sha256:e5888262d93ea0946b5fd8146cf1c19ec3a7bac4d36eb51848ef0aefa75cf8e7",
            "Volumes": null,
            "WorkingDir": "",
            "Entrypoint": [
                "/email"
            ],
            "OnBuild": null,
            "Labels": null
        },
        "Architecture": "amd64",
        "Os": "linux",
        "Size": 7861466,
        "VirtualSize": 7861466,
        "GraphDriver": {
            "Data": {
                "LowerDir": "/var/lib/docker/overlay2/03cb0162bf922636e4e0ec90123b81565a447c6cd511741103551d2f0e7f09f9/diff",
                "MergedDir": "/var/lib/docker/overlay2/091f74815a0caf457df7e57ade43b41c4dd8551388beca44815a7038501742ee/merged",
                "UpperDir": "/var/lib/docker/overlay2/091f74815a0caf457df7e57ade43b41c4dd8551388beca44815a7038501742ee/diff",
                "WorkDir": "/var/lib/docker/overlay2/091f74815a0caf457df7e57ade43b41c4dd8551388beca44815a7038501742ee/work"
            },
            "Name": "overlay2"
        },
        "RootFS": {
            "Type": "layers",
            "Layers": [
                "sha256:66f615d03920919b0fa8bc9fed45515bb95636be1837fdd10a82b2c183e2ad5b",
                "sha256:bd6a01b885eb6e3eec38a3fe3a2899646509633730b210cf6987456fd40b8a1c"
            ]
        },
        "Metadata": {
            "LastTagTime": "2017-12-14T10:24:10.796813522+01:00"
        }
    }
]
docker architecture cross-compiling arm64 docker-build
6个回答
42
投票

对于构建单个 docker 映像:使用命令行设置环境变量或修改 .bashrc 或 .zshenv 文件。 (于 03/2019 在 v19.03.0 中引入)

export DOCKER_DEFAULT_PLATFORM=linux/arm64

或者,在 Dockerfile 中,在 FROM 命令中包含以下标志(对于多阶段 Dockerfile 构建,仅第一阶段需要该标志):

FROM --platform=linux/arm64 python:3.7-alpine

要将镜像构建为 docker-compose 构建的一部分,请为每个服务包含平台:linux/arm64。例如:

services:  
  frontend:  
    platform: linux/arm64
    build: frontend  
    ports:
      - 80:80  
    depends_on:
      - backend  
  backend:  
    platform: linux/arm64
    build: backend  

反之亦然,例如,如果您有 Apple M1 芯片并希望将映像部署到基于 Linux 或 Windows 的 AMD64 环境。只需将“linux/arm64”替换为“linux/amd64”


31
投票

https://docs.docker.com/desktop/multi-arch/

# Shows builders installed
docker buildx ls

# Use builder that supports platform
docker buildx use default

docker buildx build --platform linux/arm64 -t <image_name>:<image_tag> --push .

3
投票

我能够解决问题,虽然不完全按照我想要的方式,但已经足够接近了。

  1. 拥有一台带docker的amd64 Linux机器

  2. 设置 qemu 用户静态以支持 Arm https://hub.docker.com/r/multiarch/qemu-user-static/

  3. 在您的 docker 文件中使用支持arm的基础镜像。例如。 ubuntu

  4. 使用类似于以下的命令构建图像:

    docker build --platform arm --pull -t your_tag .

此命令将强制 docker 拉取基础映像的arm版本,并将arm架构设置为结果映像。但要小心,如果您使用多个架构的标签,上面的命令会将标签设置为arm版本。因此,要运行本机 amd64 版本,您需要在没有 --platform arg 的情况下再次拉取标签。


0
投票

我在 qemu-user 的帮助下在 amd64 主机上构建并运行 arm64 映像。但是

docker inspect
这些arm64图像总是显示
"Architecture": "amd64"
。我希望如此 可以显示
"Architecture": "arm64"

我尝试了

DOCKER_DEFAULT_PLATFORM
--platform=linux/arm64
,都不起作用。我正在使用 docker 19.03.13.

最后我找到了解决方案——先保存图片,更改其元数据,然后加载 回来了:

set -e

IMAGE_ID=$(docker image inspect --format '{{.ID}}' $1)
IMAGE_ID=${IMAGE_ID#sha256:}

if [ ${#IMAGE_ID} -ne 64 ]; then
  echo "Invalid image sha256 id"
  exit 1
fi

rm -rf ${IMAGE_ID}
mkdir -p ${IMAGE_ID}
echo "IMAGE ${IMAGE_ID}"

echo "> save..."
docker save ${IMAGE_ID} | tar -xC ${IMAGE_ID}

echo "> change arch..."
sed -i 's/"architecture":"amd64"/"architecture":"arm64"/' ${IMAGE_ID}/${IMAGE_ID}.json

echo "> reload..."
tar -cC ${IMAGE_ID} . | docker load

echo "> clean..."
rm -rf ${IMAGE_ID}

echo "Note: you need to tag it manually"

将其保存到changeArch.sh,然后运行

sh changeArch.sh <sha_id>
sh changeArch.sh <image:tag>


0
投票

以前的答案都不适合我。我正在为每个架构构建一个静态 Go 二进制文件,并将其复制到构建的完全空的容器中

FROM scratch
。我需要采取以下方法,使用
docker manifest annotate
命令显式设置构建容器的架构:

docker build -f myproject.Dockerfile --pull -t registry.gitlab.com/myuser/myproject/myproject:manifest-arm64 --build-arg ARCH=arm64 .
docker build -f myproject.Dockerfile --pull -t registry.gitlab.com/myuser/myproject/myproject:manifest-amd64 --build-arg ARCH=amd64 .
docker push registry.gitlab.com/myuser/myproject/myproject:manifest-arm64
docker push registry.gitlab.com/myuser/myproject/myproject:manifest-amd64
docker manifest create registry.gitlab.com/myuser/myproject/myproject:manifest-latest \
        --amend registry.gitlab.com/myuser/myproject/myproject:manifest-arm64 \
        --amend registry.gitlab.com/myuser/myproject/myproject:manifest-amd64
docker manifest annotate --arch arm64 registry.gitlab.com/myuser/myproject/myproject:manifest-latest registry.gitlab.com/myuser/myproject/myproject:manifest-arm64
docker manifest push registry.gitlab.com/myuser/myproject/myproject:manifest-latest

0
投票

我已经在 azure 容器应用程序上部署了 docker 映像,该应用程序仅允许

amd64
。以下解决方案对我有用。

docker build -t user/image . --platform="linux/amd64"

以同样的方式,您可以为您更改平台。

© www.soinside.com 2019 - 2024. All rights reserved.