logo标签列表

Docker - 无法使用docker buildx构建多平台镜像

linuxdocker
21
我正在尝试使用docker buildx构建多平台（amd64、arm64和armv7）镜像。由于我使用的是运行Ubuntu 18.04的amd64机器，因此我按照Docker网站上的说明安装了qemu：https://docs.docker.com/buildx/working-with-buildx/#build-multi-platform-images，命令如下： sudo apt install qemu-user 但是，在我执行上述命令时出现了一个奇怪的错误。更具体地说，似乎存在与binfmt-support服务相关的问题。以下是完整日志：
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
The following additional packages will be installed:
  binfmt-support qemu-user-binfmt
The following NEW packages will be installed:
  binfmt-support qemu-user qemu-user-binfmt
0 upgraded, 3 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/7.409 kB of archives.
After this operation, 63,4 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Selecting previously unselected package binfmt-support.
(Reading database ... 245278 files and directories currently installed.)
Preparing to unpack .../binfmt-support_2.1.8-2_amd64.deb ...
Unpacking binfmt-support (2.1.8-2) ...
Selecting previously unselected package qemu-user.
Preparing to unpack .../qemu-user_1%3a2.11+dfsg-1ubuntu7.21_amd64.deb ...
Unpacking qemu-user (1:2.11+dfsg-1ubuntu7.21) ...
Selecting previously unselected package qemu-user-binfmt.
Preparing to unpack .../qemu-user-binfmt_1%3a2.11+dfsg-1ubuntu7.21_amd64.deb ...
Unpacking qemu-user-binfmt (1:2.11+dfsg-1ubuntu7.21) ...
Setting up binfmt-support (2.1.8-2) ...
Job for binfmt-support.service failed because the control process exited with error code.
See "systemctl status binfmt-support.service" and "journalctl -xe" for details.
invoke-rc.d: initscript binfmt-support, action "start" failed.
● binfmt-support.service - Enable support for additional executable binary formats
   Loaded: loaded (/lib/systemd/system/binfmt-support.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2020-02-05 17:20:29 CET; 4ms ago
     Docs: man:update-binfmts(8)
  Process: 7766 ExecStart=/usr/sbin/update-binfmts --enable (code=exited, status=2)
 Main PID: 7766 (code=exited, status=2)

feb 05 17:20:29 XPS-15-9570 systemd[1]: Starting Enable support for additional executable binary formats...
feb 05 17:20:29 XPS-15-9570 update-binfmts[7766]: update-binfmts: warning: unable to close /proc/sys/fs/binfmt_misc/register: No such file or directory
feb 05 17:20:29 XPS-15-9570 update-binfmts[7766]: update-binfmts: exiting due to previous errors
feb 05 17:20:29 XPS-15-9570 systemd[1]: binfmt-support.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
feb 05 17:20:29 XPS-15-9570 systemd[1]: binfmt-support.service: Failed with result 'exit-code'.
feb 05 17:20:29 XPS-15-9570 systemd[1]: Failed to start Enable support for additional executable binary formats.
Setting up qemu-user (1:2.11+dfsg-1ubuntu7.21) ...
Setting up qemu-user-binfmt (1:2.11+dfsg-1ubuntu7.21) ...
update-binfmts: warning: current package is qemu-user-binfmt, but binary format already installed by qemu-user-static
update-binfmts: exiting due to previous errors
dpkg: error processing package qemu-user-binfmt (--configure):
 installed qemu-user-binfmt package post-installation script subprocess returned error exit status 2
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Processing triggers for ureadahead (0.100.0-21) ...
Processing triggers for neon-settings (0.0+p18.04+git20191212.1343) ...
Processing triggers for systemd (237-3ubuntu10.33) ...
Errors were encountered while processing:
 qemu-user-binfmt
E: Sub-process /usr/bin/dpkg returned an error code (1)

尽管如此，我仍然尝试按照通常的流程继续进行，即：
docker buildx create --name mybuilder
docker buildx use mybuilder
docker buildx inspect --bootstrap

上一个命令的输出结果为：
[+] Building 5.0s (1/1) FINISHED                                                                                                                                                             
 => [internal] booting buildkit                                                                                                                                                         5.0s
 => => pulling image moby/buildkit:buildx-stable-1                                                                                                                                      4.3s
 => => creating container buildx_buildkit_mybuilder0                                                                                                                                    0.7s
Name:   mybuilder
Driver: docker-container

Nodes:
Name:      mybuilder0
Endpoint:  unix:///var/run/docker.sock
Status:    running
Platforms: linux/amd64, linux/386

您可以看到，“linux/amd64”和“linux/386”被列为唯一可用的平台，但是我还需要为“linux/arm64”和“linux/arm/v7”平台构建镜像。

我已经寻找了几个小时的解决方案，但没有找到有效的方法。

------------------------------------ 编辑 ------------------------------------

看起来我已经通过运行以下命令解决了部分问题：

sudo apt purge --auto-remove qemu-user qemu-user-binfmt binfmt-support

然后重新安装它们。实际上，再次运行此命令：

sudo apt install qemu-user

完全没有错误提示：

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
The following additional packages will be installed:
  binfmt-support qemu-user-binfmt
The following NEW packages will be installed:
  binfmt-support qemu-user qemu-user-binfmt
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/7.409 kB of archives.
After this operation, 63,4 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Selecting previously unselected package binfmt-support.
(Reading database ... 245437 files and directories currently installed.)
Preparing to unpack .../binfmt-support_2.1.8-2_amd64.deb ...
Unpacking binfmt-support (2.1.8-2) ...
Selecting previously unselected package qemu-user.
Preparing to unpack .../qemu-user_1%3a2.11+dfsg-1ubuntu7.21_amd64.deb ...
Unpacking qemu-user (1:2.11+dfsg-1ubuntu7.21) ...
Selecting previously unselected package qemu-user-binfmt.
Preparing to unpack .../qemu-user-binfmt_1%3a2.11+dfsg-1ubuntu7.21_amd64.deb ...
Unpacking qemu-user-binfmt (1:2.11+dfsg-1ubuntu7.21) ...
Setting up binfmt-support (2.1.8-2) ...
Created symlink /etc/systemd/system/multi-user.target.wants/binfmt-support.service → /lib/systemd/system/binfmt-support.service.
Setting up qemu-user (1:2.11+dfsg-1ubuntu7.21) ...
Setting up qemu-user-binfmt (1:2.11+dfsg-1ubuntu7.21) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Processing triggers for ureadahead (0.100.0-21) ...
Processing triggers for neon-settings (0.0+p18.04+git20191212.1343) ...
Processing triggers for systemd (237-3ubuntu10.38) ...

同样地，systemctl status binfmt-support.service 的输出符合预期：

● binfmt-support.service - Enable support for additional executable binary formats
   Loaded: loaded (/lib/systemd/system/binfmt-support.service; enabled; vendor preset: enabled)
   Active: active (exited) since Mon 2020-02-10 11:42:23 CET; 1min 11s ago
     Docs: man:update-binfmts(8)
 Main PID: 7161 (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4915)
   CGroup: /system.slice/binfmt-support.service

feb 10 11:42:23 XPS-15-9570 systemd[1]: Starting Enable support for additional executable binary formats...
feb 10 11:42:23 XPS-15-9570 systemd[1]: Started Enable support for additional executable binary formats.

然而，问题的一部分仍然存在，因为在运行这三个命令之后的输出如下：

docker buildx create --name mybuilder
docker buildx use mybuilder
docker buildx inspect --bootstrap

与以前相同，即：

[+] Building 2.6s (1/1) FINISHED                                                                                                                                                             
 => [internal] booting buildkit                                                                                                                                                         2.6s
 => => pulling image moby/buildkit:buildx-stable-1                                                                                                                                      2.0s
 => => creating container buildx_buildkit_mybuilder0                                                                                                                                    0.6s
Name:   mybuilder
Driver: docker-container

Nodes:
Name:      mybuilder0
Endpoint:  unix:///var/run/docker.sock
Status:    running
Platforms: linux/amd64, linux/386

为什么会这样？为什么只显示linux/amd64和linux/386作为唯一可用的平台？

编辑#2（关于@LinPy的评论）

docker context ls的输出为：

NAME                DESCRIPTION                               DOCKER ENDPOINT               KUBERNETES ENDPOINT   ORCHESTRATOR
default *           Current DOCKER_HOST based configuration   unix:///var/run/docker.sock                         swarm

我尝试在安装qemu之后重新启动docker，但没有成功。此外，在docker buildx命令中指定目标平台：

docker buildx build -t <mytag> --platform linux/amd64,linux/arm64,linux/arm/v7 --load .

导致此错误的结果为：

[+] Building 0.6s (5/20)                                                                                                      
 => [internal] load .dockerignore                                                                                        0.0s
 => => transferring context: 2B                                                                                          0.0s
 => [internal] load build definition from Dockerfile                                                                     0.0s
 => => transferring dockerfile: 32B                                                                                      0.0s
 => [linux/arm/v7 internal] load metadata for docker.io/alegeno92/opencv_python3:3.4.2                                   0.6s
 => CANCELED [linux/arm64 internal] load metadata for docker.io/alegeno92/opencv_python3:3.4.2                           0.6s
 => CANCELED [linux/amd64 internal] load metadata for docker.io/alegeno92/opencv_python3:3.4.2                           0.6s
failed to solve: rpc error: code = Unknown desc = failed to solve with frontend dockerfile.v0: failed to load LLB: runtime execution on platform linux/arm/v7 not supported

顺便说一下，我的内核版本是 4.15.0-76-generic。
4个回答
54

首先运行多架构容器

docker run --rm --privileged multiarch/qemu-user-static --reset -p yes
docker buildx rm builder
docker buildx create --name builder --driver docker-container --use
docker buildx inspect --bootstrap

您应该拥有备用架构。

多架构/qemu-user-static仓库链接：https://github.com/multiarch/qemu-user-static - MKroehnert
3

回应第一个错误，附加在这个答案上。根据https://docs.docker.com/buildx/working-with-buildx/更新了命令。

QEMU是一个跨平台模拟器，负责通过binfmt_misc处理程序获取不同架构的二进制文件。

会让一些人节省时间的是，先使用以下命令：

docker run --privileged --rm tonistiigi/binfmt --install all
1
确实，这是一个很好的开始，节省了很多时间，谢谢！ - Hardoman
1

有多个binfmt包，我认为在这个问题被问及时错过了一个配置。

对于各种包，我会选择qemu-user-static而不是qemu-user-binfmt，以避免任何动态链接问题。这两个包正在做相同的事情，所以您需要选择其中之一。

下一部分应该在当前版本中修复了，但我认为你之前遇到了这个问题。那就是当你查看/proc/sys/fs/binfmt_misc中的文件时，你会看到fix binary或F标志，例如这里看到的F标志：

$ cat /proc/sys/fs/binfmt_misc/qemu-arm
enabled
interpreter /usr/libexec/qemu-binfmt/arm-binfmt-P
flags: POCF
offset 0
magic 7f454c4601010100000000000000000002002800
mask ffffffffffffff00fffffffffffffffffeffffff

可以在此kernel.org帖子上找到关于F标志意义的详细信息，但简而言之，容器命名空间包括不同的文件系统命名空间，尝试从该命名空间访问解释器将失败（除非您做像绑定挂载/usr/libexec/qemu-binfmt到容器中那样的事情）。较新版本的qemu软件包会自动设置此标志，因此如果您的标志部分没有定义F，请参阅这些错误报告以获取需要升级的版本：

使用multiarch image中的二进制文件是一种简单的方法。如果您有专用的VM，则在CI中使用它很好（如果您正在修改其他构建使用的主机，则不太理想）。但是，如果您重新启动，它将会中断，直到再次运行容器。而且它需要您记得为任何上游补丁更新它。因此，我不建议在长时间运行的构建主机上使用它。 

docker run --rm --privileged multiarch/qemu-user-static --reset -p yes
0

对于 Github CI，添加以下插件可以解决这个问题

    - name: Set up QEMU
      id: qemu
      uses: docker/setup-qemu-action@v1
      with:
        image: tonistiigi/binfmt:latest
        platforms: all
网页内容由stack overflow 提供, 点击上面的
可以查看英文原文，
原文链接