knockknock10 opened a new pull request, #6927: URL: https://github.com/apache/camel-k/pull/6927
Fixes #6924. The November 1 Nightly release run [failed during image publication](https://github.com/apache/camel-k/actions/runs/41258109119): ```text docker manifest create docker.io/testcamelk/camel-k:2.12.0-nightly docker.io/testcamelk/camel-k:2.12.0-nightly docker.io/testcamelk/camel-k:2.12.0-nightly is a manifest list ``` The image build uses Docker Buildx, and the build log shows it exporting an image index with an attestation. The existing `images-push` target then passes the pushed base tag to classic `docker manifest create`. That tag is already a manifest list, so the command fails and the release job stops before it can publish and combine the architecture-specific tags. The later [ARM64 nightly job](https://github.com/apache/camel-k/actions/runs/41272413954) times out while waiting for the operator deployment. ### Changes - Publish the architecture-specific tags first, then create the final tag with `docker buildx imagetools create`, selecting `linux/amd64` and `linux/arm64`. This accepts manifest-list sources and keeps the Buildx image-index workflow. - Use the same manifest creation approach in the staging publishing target. - Check that the nightly operator image contains a `linux/arm64` manifest before deploying it. - If the operator does not become Available, print the pods, deployment description, and namespace events in the job log. ### Validation - A Make dry-run with `ARCH_VERSIONS=amd64 arm64` confirmed that both architecture tags are pushed and the final tag is assembled from those sources. - The updated ARM64 install script passed `bash -n`. - The `jq` architecture check passed against a sample image index. A real registry push and a hosted ARM64 workflow run have not yet been executed from this branch; those results still need to be confirmed by CI. -- 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]
