knockknock10 commented on issue #6923: URL: https://github.com/apache/camel-k/issues/6923#issuecomment-6561275988
I compared the October 31 failure here with the report in #6924. Both point to the same failure in `images-push`: classic `docker manifest create` is being given a tag that Buildx has already published as a manifest list. Rather than open a duplicate PR, I linked the shared fix in [PR #6927](https://github.com/apache/camel-k/pull/6927). It switches the publishing step to `docker buildx imagetools create` using the architecture-specific tags, and includes the related ARM64 manifest check and deployment diagnostics. The PR description references both issues. The focused Make dry-run, shell syntax check, and `jq` fixture checks passed. However, the actual registry push and hosted ARM64 workflow are not yet verified: all 13 PR workflows are currently awaiting maintainer approval, and no CI jobs have started. @squakez, could you approve the PR workflows so the end-to-end validation can run? I also saw @Yasas-Sri's earlier request to work on this issue; please let us know if you would prefer any separate follow-up rather than handling these two reports through the same fix. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
