mfwadejr
caf98ed6a9
Publish container / publish (push) Successful in 48s
QEMU cross-arch emulation hung indefinitely on the self-hosted Gitea runner (likely no privileged Docker access), so the actual arch wasn't the problem worth chasing. The far more common cause of "no matching manifest" against a self-hosted registry is Buildx's default provenance/SBOM attestation manifests, which not every registry implementation (including Gitea's) resolves correctly when a client requests a single-platform pull. Disabling both keeps the image a plain single-manifest image, matching what a manual `docker push` already produced and pulled fine.