Images for linux/arm64 platform are actually linux/amd64

[mouchar]

Describe the bug
Images available on Docker Hub (featurehub/mr:1.9.1, featurehub/dacha2:1.9.1, possibly all others) show they are available for linux/arm64 and linux/amd64 platforms. However, linux/arm64 actually contains amd64 binaries so it can't run on arm64 CPUs.

To Reproduce
Steps to reproduce the behavior:

1. Inspect manifest on DockerHub:

docker manifest inspect featurehub/mr:1.9.1 |  jq '.manifests[]|{digest, platform}'
{
  "digest": "sha256:4d0360d02c94dc89755c9a20dcca6db98cf30f353dab277a1c684798aedef1d6",
  "platform": {
    "architecture": "amd64",
    "os": "linux"
  }
}
{
  "digest": "sha256:7afd08d0a73ac47162f3ecf367cc55064f348571c11538b14d686d8443610829",
  "platform": {
    "architecture": "arm64",
    "os": "linux"
  }
}

2. Try starting container on arm64 machine:

/ # uname -m
aarch64
/ # docker run -it --rm --entrypoint sh  featurehub/mr:1.9.1 
Unable to find image 'featurehub/mr:1.9.1' locally
1.9.1: Pulling from featurehub/mr
Digest: sha256:477d8bf771a9ececf5995fdf6a30380700099cb5b59d63026d7e32b260adae41
Status: Downloaded newer image for featurehub/mr:1.9.1
exec /bin/sh: exec format error

3. Further inspection in image layers prove that image was built from x86_64 (amd64) base:

/ # docker history featurehub/mr@sha256:477d8bf771a9ececf5995fdf6a30380700099cb5b59d63026d7e32b260adae41
IMAGE          CREATED         CREATED BY                                      SIZE      COMMENT
477d8bf771a9   N/A             jib-maven-plugin:3.4.6                          8.19kB    extra files
<missing>      N/A             jib-maven-plugin:3.4.6                          76.4MB    extra files
<missing>      N/A             jib-maven-plugin:3.4.6                          16.4kB    jvm arg files
<missing>      N/A             jib-maven-plugin:3.4.6                          143kB     extra files
<missing>      N/A             jib-maven-plugin:3.4.6                          2.25MB    snapshot dependencies
<missing>      N/A             jib-maven-plugin:3.4.6                          108MB     dependencies
<missing>      6 months ago    RUN /bin/sh -c (delgroup ping | true) && add…   24.6kB    buildkit.dockerfile.v0
<missing>      9 months ago    ENTRYPOINT ["/__cacert_entrypoint.sh"]          0B        buildkit.dockerfile.v0
<missing>      9 months ago    COPY --chmod=755 entrypoint.sh /__cacert_ent…   8.19kB    buildkit.dockerfile.v0
<missing>      9 months ago    RUN /bin/sh -c set -eux;     echo "Verifying…   0B        buildkit.dockerfile.v0
<missing>      9 months ago    RUN /bin/sh -c set -eux;     ARCH="$(apk --p…   129MB     buildkit.dockerfile.v0
<missing>      9 months ago    ENV JAVA_VERSION=jdk-11.0.27+6                  0B        buildkit.dockerfile.v0
<missing>      9 months ago    RUN /bin/sh -c set -eux;     apk add --no-ca…   35.2MB    buildkit.dockerfile.v0
<missing>      9 months ago    ENV LANG=en_US.UTF-8 LANGUAGE=en_US:en LC_AL…   0B        buildkit.dockerfile.v0
<missing>      9 months ago    ENV PATH=/opt/java/openjdk/bin:/usr/local/sb…   0B        buildkit.dockerfile.v0
<missing>      9 months ago    ENV JAVA_HOME=/opt/java/openjdk                 0B        buildkit.dockerfile.v0
<missing>      11 months ago   CMD ["/bin/sh"]                                 0B        buildkit.dockerfile.v0
<missing>      11 months ago   ADD alpine-minirootfs-3.21.3-x86_64.tar.gz /…   8.14MB    buildkit.dockerfile.v0

4. See the alpine-minirootfs-3.21.3-x86_64.tar.gz which comes from amd64 alpine base.

Versions

• FeatureHub version 1.9.1, possibly others
• OS: Linux
• Docker 29.2.1

Additional context
Please fix the build process and publish working multi-platform images.

[rvowles]

The base images are featurehub/base_jdk:2.0 (and now 2.1 as we will be coming out with java 25 shortly), and they are built using this mechanism https://github.com/featurehub-io/featurehub/blob/main/pipeline/build/base_jdk/make-dualarch-and-push.sh

and we don't use a SHA in our build but that image name so I wonder if there has been a bug in Jib around this. We will be publishing RC's for 1.9.2 over the next few days so I'll take your feedback and check what gets created.

[mouchar]

both featurehub/base_jdk:2.0 and featurehub/base_jdk:2.1 are broken

https://github.com/featurehub-io/featurehub/blob/8880c342d95c0f8550b279c3fb797c5535557e2e/pipeline/build/base_jdk/Dockerfile#L1C18-L1C31

You use --platform=$BUILDPLATFORM instead of --platform=$TARGETPLATFORM

[mouchar]

FTR, other base images like this are also wrong, for the same reason.

Explanation: it's fine to use --platform=$BUILDPLATFORM in the first stages of multi-stage builds. But the final stage must not use this argument (or must use --platform=$TARGETPLATFORM) so that final images are actually multi-platform.

[rvowles]

I regenerated the two base_jdk and base_party (2.1 version) and pushed them based on your suggestions. It seems odd the original request to add multi-platform was OK and then it no longer worked! We are working actively on getting a security update based on Java 25 out so hoping to have at least RC images of 1.9.2 shortly.

[mouchar]

I confirm featurehub/mr:1.9.2-RC is valid multi-platform image. I didn't check other images, but I assume they're fine as well. Thank you for the fix.