Details
-
Bug
-
Resolution: Done
-
Critical
-
2.2.0.Alpha3
-
None
-
False
-
None
-
False
Description
Multiplatform build of example-postres fails as the script tries to build debezium/example-postgres image on ARM (which is based on debezium/postgres:15 which is not available for ARM). We shouldn't build it on ARM at the first place, but as it worked before, it signals some other error, likely introduced during work on DBZ-6216 which needs to be fixed as well.
In the past it always worked this way, that images were build for AMD as well as for ARM, but in the part arm build failed silently (e.g. here) with
#4 [linux/arm64 internal] load metadata for quay.io/debezium/postgres:15 #4 DONE 1.8s ... #6 [linux/arm64 1/2] FROM quay.io/debezium/postgres:15@sha256:1236305948e831ce89dbed8b6279ac3b53a2702a1d650263bd25601c1bee3f98 #6 resolve quay.io/debezium/postgres:15@sha256:1236305948e831ce89dbed8b6279ac3b53a2702a1d650263bd25601c1bee3f98 done #6 DONE 0.0s ... #8 [linux/arm64 2/2] COPY inventory.sql /docker-entrypoint-initdb.d/ #8 CANCELED
Now, it fails immediately with
5 [linux/arm64 internal] load metadata for docker.io/debezium/postgres:15 #5 ERROR: no match for platform in manifest sha256:698d6099ec929a18d74ee3d12836944b7ec6be9e54ecf5fff9a18c2b9672791b: not found ------ > [linux/arm64 internal] load metadata for docker.io/debezium/postgres:15: ------ Dockerfile:1 -------------------- 1 | >>> FROM debezium/postgres:15 2 | 3 | LABEL maintainer="Debezium Community" -------------------- ERROR: failed to solve: debezium/postgres:15: no match for platform in manifest sha256:698d6099ec929a18d74ee3d12836944b7ec6be9e54ecf5fff9a18c2b9672791b: not found
It seem that recent debezium/postgres:15 is missing some metadata as in successful build Docker was able to load metadata and failed silently later on, while now fails hard when loading metadata.
