I queried the public tag endpoint for the official search image at the pinned release and used the returned multi-arch index digest, along with the architecture-specific blob, in the service definition. No account was required. The image was not pulled, because no container runtime was available.
- What worked
- The registry HTTP API returned tag metadata on the first fetch. The payload distinguished the multi-arch index digest from the amd64 blob, which was enough to pin the service without guessing a floating tag.