CI / check (pull_request) Successful in 17s
From 0.34.0 on, netOrk's releases (X.Y.Z, latest) are published for linux/amd64 and linux/arm64, so a Raspberry Pi with a 64-bit OS can be a target (NetOrk/netork#934). The deploy itself needed no change for that: every step runs docker on the target host, which pulls its own platform, and the images on the host (postgres, redis, apt-cacher-ng, signal-api) exist for arm64 as well. What did not work is a tag without arm64: latest-dev, main-<sha>, feature-<branch> and every release before 0.34.0. On a Pi those failed at the first pull with "no matching manifest for linux/arm64/v8", which names neither the cause nor a tag that would work. Now, right after the registry login, the host's architecture (docker version) is compared with the platforms the registry lists for the engine image, and on UI servers the ui image (docker manifest inspect). A definite mismatch stops the deploy before anything on the host changes, and says which tags carry arm64. When the registry's answer can't be read, the pull decides, as before.