feat(release): publish watchdog image to GHCR and Docker Hub#17
Conversation
Push ghcr.io/cartesi/sequencer-watchdog:<tag> (multi-arch manifest) alongside existing docker-save tarballs. Mirrors cartesi/cli container publishing so operators can COPY --from= in custom rootfs builds (e.g. Fly.io). Requires DOCKERHUB_USERNAME and DOCKERHUB_TOKEN repo secrets for Docker Hub mirror.
endersonmaia
left a comment
There was a problem hiding this comment.
I strongly suggest using the docker/build-push-action instead of handling stuff via docker commands.
Address PR review: push ghcr.io and docker.io tags without arch suffixes (buildx assembles the multi-arch manifest), replace shell docker build/push with docker/build-push-action, and drop the separate imagetools manifest job.
19faf39 to
9abc31a
Compare
Can you take a look if the new change makes sense? |
Drop docker-save tarballs from GitHub Releases; publish watchdog via GHCR and Docker Hub only. Single build-push job with setup-qemu for amd64+arm64 manifest. Pass per-arch cartesi-machine deb SHA256 via Dockerfile TARGETARCH.
8a8e3c3 to
b038061
Compare
endersonmaia
left a comment
There was a problem hiding this comment.
LGTM
I tested building locally, it seems ok but the release CI will only run with a tag, right?
Let's see if it works 😅
Then I can use it from a Dockerfile like suggested in the docs.
endersonmaia
left a comment
There was a problem hiding this comment.
While closing my review editor, I see that there's a reference for a 0.20.0-test2 version of machine-emulator
Shouldn't that be a final 0.20.0 tag?
Use the final v0.20.0 machine-emulator release (not v0.20.0-test2) with updated deb SHA256s. Derive canonical-app cartesi-machine and machine-linux-image versions from toolchain-pins.env, extend verify-toolchain-pins.sh cross-checks, and update staging-drills for GHCR.
Great catch! I've updated. Let's try to merge and trigger the release process :] |
Push ghcr.io/cartesi/sequencer-watchdog: (multi-arch manifest) alongside existing docker-save tarballs. Mirrors cartesi/cli container publishing so operators can COPY --from= in custom rootfs builds (e.g. Fly.io).
Requires DOCKERHUB_USERNAME and DOCKERHUB_TOKEN repo secrets for Docker Hub mirror.