ci: publish images to Docker Hub instead of GHCR#132
Merged
Conversation
Retargets the multi-arch publish workflow at netboxlabs/netbox-mcp-server on Docker Hub (the convention for NetBox Labs public images, matching orb-agent). Switches to native amd64/arm64 runners with push-by-digest and a manifest merge to drop QEMU emulation. Publishes only on v*.*.* tag pushes; the daily rescan and the README pull instructions are updated to point at Docker Hub. Refs #83 Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
3 tasks
Pre-release tags (those containing `-`, e.g. v1.2.0-rc1) now publish only their full version. They no longer overwrite :latest, :MAJOR, or :MAJOR.MINOR — those should always point at a stable release. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
abubnalitic-nbl
approved these changes
May 7, 2026
3 tasks
abubnalitic-nbl
added a commit
that referenced
this pull request
May 8, 2026
Adds supply-chain hardening to the Docker Hub publish pipeline introduced in #132: - Pin the python:3.14-alpine3.23 base image by digest in both Dockerfile stages so a compromised tag cannot substitute the base. - Sign the published multi-arch manifest with cosign keyless (Sigstore + GitHub OIDC) so pullers can verify each image came from this repo's Actions. - Generate SLSA build provenance attestations via actions/attest-build-provenance, pushed to the registry alongside the manifest, linking any published digest back to the workflow run that produced it. - Document `cosign verify` in the README's Docker Hub section. Carries over the intent of #127, restructured to fit the matrix-build / manifest-merge workflow merged in #132. Signing happens once on the manifest-list digest in the merge job; all aliased tags (latest, X.Y.Z, X.Y, X) resolve to the same digest, so a single signature covers them. Co-authored-by: Claude Sonnet 4.6 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docker-publish.ymlto publish multi-arch images tonetboxlabs/netbox-mcp-serveron Docker Hub. NetBox Labs publishes its public container images on Docker Hub (e.g. orb-agent); this aligns the MCP server with that convention.linux/amd64+linux/arm64runners, push-by-digest, and a manifest merge — same pattern used bynetboxlabs/orb-agent.v*.*.*tag pushes (plusworkflow_dispatch).latestnow tracks the most recent stable release rather than every commit onmain. Container scanning on PRs is unchanged (covered bycontainer-scan.yaml).-, e.g.v1.2.0-rc1) publish only their full version. They never move:latest,:MAJOR, or:MAJOR.MINOR— those should always point at a stable release.Prerequisites
Two repository secrets must exist before the workflow can authenticate to Docker Hub:
DOCKERHUB_USERNAMEDOCKERHUB_TOKEN(Read & Write scope, with access tonetboxlabs/netbox-mcp-server)The Docker Hub repository
netboxlabs/netbox-mcp-servermust also exist (token scopes typically don't allow creating new repositories in the namespace).Relationship to #127
#127 hardens the publish pipeline (cosign keyless signatures, SLSA build provenance, base-image digest pin). That hardening is independently valuable and should land before the first public Docker Hub release; it just needs to be rebased onto this branch so the cosign/attest steps target Docker Hub instead of GHCR.
Test plan
actionlintpasses on the modified workflowsv0.0.0-testtag at HEAD and confirmed a clean runBuild (linux/amd64)andBuild (linux/arm64)both green on native runnersMerge multi-arch manifestpublisheddocker.io/netboxlabs/netbox-mcp-server:0.0.0-testas a multi-arch OCI image index (amd64 + arm64 + buildkit attestation manifests):latest, no:0, no:0.00.0.0-testDocker Hub tag will be cleaned up manually:latest/:MAJOR.MINOR/:MAJORfloating-tag path (not covered by the pre-release smoke test)