使用buildx构建多架构的镜像

用户9822880

发布于 2022-06-13 15:18:20

9760

发布于 2022-06-13 15:18:20

文章被收录于专栏：3分钟云计算

最近项目需要支持ARM平台，所以之前使用的那些镜像需要重新构建。构建多架构镜像的方法有很多，这里列出个人觉得最简单的一种方法。

思路：

不同平台的可运行二进制文件不同，所以需要在构建过程中编译二进制文件
基本镜像需要支持多架构，这样才能在其基础上进行编译

下面以一个Golang 代码的operator为例：https://github.com/jianzhangbjz/learn-operator 以下步骤在MacOS 上进行，Docker version 20.10.13

创建一个builder

mac:learn-operator jianzhang$ docker buildx create --use --name jian
jian
mac:learn-operator jianzhang$ docker buildx ls
NAME/NODE       DRIVER/ENDPOINT             STATUS   PLATFORMS
elegant_wu      docker-container                     
  elegant_wu0   unix:///var/run/docker.sock stopped  
jian *          docker-container                     
  jian0         unix:///var/run/docker.sock inactive 
desktop-linux   docker                               
  desktop-linux desktop-linux               running  linux/amd64, linux/arm64, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/arm/v7, linux/arm/v6
default         docker                               
  default       default                     running  linux/amd64, linux/arm64, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/arm/v7, linux/arm/v6

‍使用一个多架构的基础镜像，你可以使用 $docker buildx imagetools inspect 来查看。例如：

mac:learn-operator jianzhang$ docker buildx imagetools inspect registry.access.redhat.com/ubi8/ubi-minimal:latest
Name:      registry.access.redhat.com/ubi8/ubi-minimal:latest
MediaType: application/vnd.docker.distribution.manifest.list.v2+json
Digest:    sha256:574f201d7ed185a9932c91cef5d397f5298dff9df08bc2ebb266c6d1e6284cd1
           
Manifests: 
  Name:      registry.access.redhat.com/ubi8/ubi-minimal:latest@sha256:c1cd272f2ffd1d4ae660bdd31d08f2072e9a6a0805d4d31730dc475e55296948
  MediaType: application/vnd.docker.distribution.manifest.v2+json
  Platform:  linux/amd64
             
  Name:      registry.access.redhat.com/ubi8/ubi-minimal:latest@sha256:9bf78e321fd7fe46075971a83c6f92e48cbc35b546bf9af72b865fc45673d562
  MediaType: application/vnd.docker.distribution.manifest.v2+json
  Platform:  linux/arm64
             
  Name:      registry.access.redhat.com/ubi8/ubi-minimal:latest@sha256:aeba4dfe9297d322afe7f633e6b3ebe0c80dc282e60d5755765d3a26b4d7d05b
  MediaType: application/vnd.docker.distribution.manifest.v2+json
  Platform:  linux/ppc64le
             
  Name:      registry.access.redhat.com/ubi8/ubi-minimal:latest@sha256:1049e0a6e05d8e839060f51e3b838439f7e38d0a3497b2504da8107603c8ba92
  MediaType: application/vnd.docker.distribution.manifest.v2+json
  Platform:  linux/s390x

从上面的结果可以看到基础镜像registry.access.redhat.com/ubi8/ubi-minimal:latest 支持四种架构：

linux/amd64,linux/arm64,linux/ppc64le,linux/s390x

该基础镜像满足多架构需求，Dockerfile 如下：

FROM golang:1.17 as build
COPY . /app/
WORKDIR /app
RUN go build -mod=vendor -o "/app/build/bin/learn-operator" "/app/cmd/manager/main.go"

FROM registry.access.redhat.com/ubi8/ubi-minimal:latest
COPY --from=build  /app/build/bin /usr/local/bin/
ENTRYPOINT ["/usr/local/bin/learn-operator"]

使用buildx构建多架构镜像，因为该基础镜像支持四种平台所以这里我也构建了四种平台，也可以根据自身需求编译其中的几个。

mac:learn-operator jianzhang$ docker buildx build --platform linux/amd64,linux/arm64,linux/ppc64le,linux/s390x -t quay.io/olmqe/learn-operator:v2 --push .
[+] Building 1034.8s (11/35)                                                                                                                   
[+] Building 1035.0s (11/35)                                                                                                                   
[+] Building 2175.2s (29/35)                                                                                                                   
[+] Building 3497.0s (29/35)                                                                                                                   
[+] Building 3562.8s (29/35)                                                                                                                   
[+] Building 4890.8s (37/37) FINISHED                                                                                                          
 => [internal] load build definition from Dockerfile                                                                                      0.0s
 => => transferring dockerfile: 330B                                                                                                      0.0s
 => [internal] load .dockerignore                                                                                                         0.0s
 => => transferring context: 2B                                                                                                           0.0s
 => [linux/s390x internal] load metadata for registry.access.redhat.com/ubi8/ubi-minimal:latest                                           9.8s
 => [linux/s390x internal] load metadata for docker.io/library/golang:1.17                                                                4.5s
 => [linux/arm64 internal] load metadata for registry.access.redhat.com/ubi8/ubi-minimal:latest                                           6.7s
 => [linux/arm64 internal] load metadata for docker.io/library/golang:1.17                                                                7.1s
 => [linux/amd64 internal] load metadata for registry.access.redhat.com/ubi8/ubi-minimal:latest                                           5.0s
 => [linux/amd64 internal] load metadata for docker.io/library/golang:1.17                                                                7.2s
 => [linux/ppc64le internal] load metadata for registry.access.redhat.com/ubi8/ubi-minimal:latest                                         9.6s
 => [linux/ppc64le internal] load metadata for docker.io/library/golang:1.17                                                              8.2s
 ...
 => => pushing layers                                                                                                                   139.5s
 => => pushing manifest for quay.io/olmqe/learn-operator:v2@sha256:f6a1edff25fe0d666b50dd8128122e20e8248808859c895f48c7ec5ef6c3e3a5       6.3s
 => [auth] olmqe/learn-operator:pull,push token for quay.io

以上是编译支持多平台架构镜像的全部步骤，是不是很简单？快来试试吧。

本文参与腾讯云自媒体同步曝光计划，分享自微信公众号。

原始发表：2022-04-25，如有侵权请联系 cloudcommunity@tencent.com 删除

打包