v1.16.11 image FTBFS

[kenhys]

Describe the bug

armhf image fails to build, it blocks publishing v1.16.11 images.

To Reproduce

See GitHub Publish workflow for v1.16.11.

https://github.com/fluent/fluentd-docker-image/actions/runs/20223210073

Expected behavior

GitHub Publish workflow for v1.16.11 will succeed.

Your Environment

- Tagging v1.16.11-1.0

Your Configuration

N/A

Your Error Log

https://github.com/fluent/fluentd-docker-image/actions/runs/20223210073

> [builder 3/4] RUN apk add curl --no-cache:
2.218 ( 5/10) Installing nghttp2-libs (1.68.0-r0)
2.232 ( 6/10) Installing nghttp3 (1.13.1-r0)
2.246 ( 7/10) Installing libpsl (0.21.5-r3)
2.260 ( 8/10) Installing zstd-libs (1.5.7-r2)
2.288 ( 9/10) Installing libcurl (8.17.0-r1)
2.317 (10/10) Installing curl (8.17.0-r1)
2.336 Executing busybox-1.37.0-r29.trigger
2.339 * execve: No such file or directory
2.340 ERROR: lib/apk/exec/busybox-1.37.0-r29.trigger: exited with error 127
2.353 1 error; 9 MiB in 27 packages
------
 3 warnings found (use docker --debug to expand):
 - FromPlatformFlagConstDisallowed: FROM --platform flag should not use constant value "linux/arm/v7" (line 11)
 - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 7)
 - LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format (line 13)
Dockerfile:8
--------------------
   6 |     WORKDIR /go
   7 |     ENV QEMU_DOWNLOAD_SHA256 47ae430b0e7c25e1bde290ac447a720e2ea6c6e78cd84e44847edda289e020a8
   8 | >>> RUN apk add curl --no-cache
   9 |     RUN curl -sL -o qemu-3.0.0+resin-arm.tar.gz https://github.com/balena-io/qemu/releases/download/v3.0.0%2Bresin/qemu-3.0.0+resin-arm.tar.gz && echo "$QEMU_DOWNLOAD_SHA256 *qemu-3.0.0+resin-arm.tar.gz" | sha256sum -c - | tar zxvf qemu-3.0.0+resin-arm.tar.gz -C . && mv qemu-3.0.0+resin-arm/qemu-arm-static .
  10 |     
--------------------
ERROR: failed to build: failed to solve: process "/dev/.buildkit_qemu_emulator /bin/sh -c apk add curl --no-cache" did not complete successfully: exit code: 1

Additional context

No response